On Mon, 01 Aug 2005 22:08:52 +0300, Yuval Kogman <[EMAIL PROTECTED]> wrote:
[...] > On Mon, Aug 01, 2005 at 08:46:07 -0700, Greg Buchholz wrote: > >> Has any thought been given to using a concurrent garbage collector >> for Perl6? Besides eliminating GC pauses (which in turn means less of a >> need for users to fiddle with the GC settings, and therefore a smaller >> chance of accidently screwing it up), it might be one of the easier >> sources of parallelism to exploit on multi-processor machines. And it >> could open the door for more soft realtime applications in Perl (audio >> processing, games, etc.).=20 > > Well, the reason an API based on what an object requires, not how > it gets it is better is that it doesn't matter - Then what I was calling GC::exclude(&CODE) should be called GC::nodelay(&CODE) . ie I'm requesting that the Garbiage collector doesn't cause a pause while &CODE is being executed. And leave the reson why a pause doesn't happen to the implementor of the GC. -- Please excuse my spelling as I suffer from agraphia. See http://dformosa.zeta.org.au/~dformosa/Spelling.html to find out more. Free the Memes.
