On Sat, 9 Aug 2008, John Cowan wrote:
Kon Lovett scripsit:
I guess I just prefer social rather than legal prescriptions.
Prohibition is an attack on symptoms not causes.
Why have we eliminated dynamic binding of lambda variables? Why
don't we allow you to take the car or cdr of (), or of
Elf scripsit:
you cant take the car or cdr of an atomic object: the slots dont exist.
And yet in CL and all the way back to Lisp 1.5, (car nil) = (cdr nil) = nil.
In pre-CL Lisps, the CDR of a symbol was its property list; CL finally
abolished that.
these arent relevant comparisons. more
Good evening, gentle creatures,
Whatever overhaul the interface and model get, I think the
implementation needs some work, too. I/O blocking everything (with
the exception of TCP and the REPL) is somewhat annoying. Having green
threads keeps Scheme programs from taking advantage of multiple
Am Sonntag, den 10.08.2008, 10:38 -0400 schrieb John Cowan:
a more relevant comparison (and answer) might be 'why don't we get
rid of 'kill -9'?'
...
(except by debuggers that need to freeze threads so
it can inspect their contents, something Scheme doesn't support):
That's what I think:
On Sun, 10 Aug 2008, John Cowan wrote:
Elf scripsit:
you cant take the car or cdr of an atomic object: the slots dont exist.
And yet in CL and all the way back to Lisp 1.5, (car nil) = (cdr nil) = nil.
In pre-CL Lisps, the CDR of a symbol was its property list; CL finally
abolished that.
We are not doing native threads.
Period.
Brief explanation:
I've been spending most of the last 6 months, now, just trying to get
I/O working properly on the various platforms we support. Threading is
right out of the question. There are too many threading models on our
supported
Well, the design of such an alternative library should be guided by
the users' needs. What are the usage scenarios? What aspects of those
scenarios cannot be met by the standard Unix process model?
Shared-memory concurrency is a complicated issue, and the design of
such a library should be
On 2008-Aug-10, at 11:44, Elf wrote:
NO KNOWN MULTIPLATFORM LANGUAGE IMPLEMENTATIONS HAVE WORKING NATIVE
THREADING.
NO KNOWN MULTIPLATFORM LIBRARY IMPLEMENTATIONS HAVE WORKING NATIVE
THREADING.
Seconding Elf's comments. A shared garbage-collected memory is only
one of the factors that
