[11169] in cryptography@c2.net mail archive
Re: It's Time to Abandon Insecure Languages
daemon@ATHENA.MIT.EDU (jamesd@echeque.com)
Sat Jul 20 17:26:56 2002
From: jamesd@echeque.com
To: Ben Laurie <ben@algroup.co.uk>
Date: Sat, 20 Jul 2002 13:59:29 -0700
Cc: Matthew Byng-Maddick <cryptography@lists.colondot.net>,
cryptography@wasabisystems.com
In-reply-to: <3D395A7A.2070905@algroup.co.uk>
--
On 20 Jul 2002 at 13:41, Ben Laurie wrote:
> E is interesting for far more reasons that just buffer overflows
> - in particular, it is capabilities from the ground up. Not to
> mention highly cool for distributed applications.
It seems like a really brilliant concept if it works, a solution
to the presently unsolved problem of distributed computing.
However I have a suspicion that instead of the presently
intolerable problem of bugs resulting in rare, non deterministic
deadlocks, we will get the problem of bugs resulting in rare, non
deterministic catch probs.
With E, as with C, we get multithreaded code executed in non
deterministic order. It appears to me that it still happen that a
certain rare and unusual execution order can reveal a bug, the bug
being of the form that if G is executed before Y is executed,
which normally never happens, then the "when" clause for X can
never be executed until the "when" clause for Y is executed, but
the "when" clause for Y can never be executed until the "when"
clause for X is executed -- the old familiar multithreading
problem that has destroyed so many projects and careers. in a new
and slightly different guise.
Is there some feature of the syntax or error handling of E that
prevents one writing such code, or reliably detects the error if
one does write it?
--digsig
James A. Donald
6YeGpsZR+nOTh/cGwvITnSR3TdzclVpR0+pr3YYQdkG
TJaqxyH7No6TPtZ2M1lp9CnI8y97z98H8Iu8O1fd
2VYVSKyVceokHx47wtPodKLoRStR7QRTLp+38k41a
---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to majordomo@wasabisystems.com
