Charles O Nutter wrote: > On 7/17/06, *Ola Bini* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: > > I think the single-array-per-call would work just fine...but we have > some other considerations too like handling argument lists, passed > blocks and block args, and ensuring constant lookup time for > blocks-within-blocks-within-methods. At any rate, smack me around if I > start to fall into pre-optimization mode. One array per call probably > isn't gonna kill us.
Ah, and that's the fine point about having a stack of frame. If you make certain that the stack is indexable from the in i O(1) time, we have constant lookup for any nesting possible. Argument lists should be handled in the same way, actually, as the last frame pushed, since blocks need to have access to these too. -- Ola Bini (http://ola-bini.blogspot.com) JvYAML, RbYAML, JRuby and Jatha contributor System Developer, Karolinska Institutet (http://www.ki.se) OLogix Consulting (http://www.ologix.com) "Yields falsehood when quined" yields falsehood when quined. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Jruby-devel mailing list Jruby-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jruby-devel
