Re: GC leak?

I went ahead and looked it up: http://www.parrotcode.org/docs/pdd/pdd25_concurrency.html Note that this is a design document although there is some discussion of implementation. I don't know how much of the design has been implemented, but the file src/scheduler.c (http://svn.perl.org/viewvc/parrot/trunk/src/scheduler.c?view=log) does have code in it. The JVM provides (if memory serves) just one construct to manage concurrency, the monitor, which uses locks on objects to do its job. Voila! Support for multithreading, etc. in one fell swoop since everything else is implemented in class libraries. So, yes, concurrency is about data safety and liveliness, but the theory of the underlying implementation can be quite simple. Of course, the implications of the model (the practice) can take years to get completely correct, as in the Java case. XEmacs on top of Parrot anyone? ;-) --- Vladimir P.S. In theory, practice and theory are the same. In practice, they are different. on 02/03/2008 01:00 AM Stephen J. Turnbull said the following: -- Vladimir G. Ivanovic _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta