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
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 acci
David Formosa wrote:
> I can see advantages to both approches. All GC systems have a hit
> when they run, in some situations it would be nice to shift the hit to
> times when it doesn't mattor that much. For example a GUI app may
> delay the GC till when the user has been idle for a while.
On Thu, 28 Jul 2005 16:22:19 +0300, Yuval Kogman <[EMAIL PROTECTED]> wrote:
[...]
> On Thu, Jul 28, 2005 at 01:08:13 -, David Formosa (aka ? the Platypus) =
> wrote:
[...]
>> my Bigobjet $big is GC::timely =3D Bigobect; # Request timely
>> # destruction of $big. Usefull for filehandels and
On Thu, Jul 28, 2005 at 01:08:13 -, David Formosa (aka ? the Platypus)
wrote:
> On 26 Jul 2005 05:18:05 -, David Formosa )
> <[EMAIL PROTECTED]> wrote:
>
> > We are should have an API to talk to the GC and give it hints about when it
> > should run, and tweek the verious paramitors for i
On 26 Jul 2005 05:18:05 -, David Formosa )
<[EMAIL PROTECTED]> wrote:
> We are should have an API to talk to the GC and give it hints about when it
> should run, and tweek the verious paramitors for its running.
>
> For example
[...]
Also
my Bigobjet $big is GC::timely = Bigobect; # Requ
