On Sep 5, 2012, at 8:08 AM, Iain Buclaw <[email protected]> wrote:
> 
> Array literals are not so easy to fix.  I once thought that it would
> be optimal to make it a stack initialisation given that all values are
> known at compile time, this infact caused many strange SEGV's in quite
> a few of my programs  (most are parsers / interpreters, so things that
> go down *heavy* nested into itself, and it was under these
> circumstances that array literals on the stack would go corrupt in one
> way or another causing *huge* errors in perfectly sound code).

It sounds like your code has escaping references?  I think the presence of a GC 
tends to eliminate a lot of thought about data ownership.  This is usually 
beneficial in that maintaining ownership rules tends to be a huge pain, but 
then it also tends to avoid issues like this.

Reply via email to