On Wed, Mar 26, 2008 at 09:12:18AM -0700, Geoffrey Broadwell wrote: > > Being able to write > > > > unshift @?BLOCK, $?BLOCK; > > > > would be useful, as it prevents the need for creating the List class > > over and over again. > > I feel that these ops are so basic, it would be well worth it to have > > them around. > > I disagree with the syntax, but agree with the sentiment. I'm fine with > requiring everything in NQP to use method or sub call syntax (as opposed > to adding listop syntax) -- but having to write the PIR wrappers for > array shift and unshift seemed really silly and wartish. The most basic > array methods (shift, unshift, push, pop, elems) should all just be > there, because there's no reason for every language implementor to > rewrite them.
This might in fact be an argument that Parrot's base PMC types should provide these methods by default. Pm