Deprecation Policy and new GC

[Christoph Otto]

On 02/14/2011 06:54 PM, Andrew Whitworth wrote:
> I find this situation to be extremely frustrating. I sincerely hope we
> can start a concerted discussion about this topic and find a
> resolution that is going to be acceptable to our developers and our
> users.

I'd propose this compromise:  We merge the new gc in after mikehh cuts 3.1 but 
make gc_ms2 the configure-time default for 3.2 and 3.3, unless an option 
specifying otherwise is passed to Configure.pl.  This would let users who 
aren't expecting the write barrier changes continue to use Parrot as-is, but 
would also let Rakudo take advantage of the speed improvements from the 
generational gc.  The default for non-release builds would be the generational 
gc, since that's what will need the most testing and developer tuits.

I'll be bringing this idea up tomorrow at #ps.  Hopefully it's a good enough 
compromise between stability and speed that gives everyone the options they need.

Christoph



>
> --Andrew Whitworth
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>