Re: The split opcode

[James deBoer]

Leopold Toetsch wrote:
James deBoer <[EMAIL PROTECTED]> wrote:
 

I would even go further than that and say that if we went with
PGE::Rule's "split", the split opcode should be obsoleted.
   

All these function/method like opcodes will be refactured somewhen.
WRT split (you write):
 PGE::Rule."split"()
in general
 $P0."split"(...)
where $P0 is a namespace or object that "can split". For some bits of
more performance a user could do:
 cl = getclass "String"
 cl."split"(...)
assuming that the current split on strings moves to the String class.
 

Ok. If we are moving things like split into objects at some point in the 
future, should the split opcode be removed now?

(I'm guessing the answer is yes, since split is one of the opcodes 
listed in your 'Too many opcodes' post of a few weeks back)

At this point the split opcode doesn't really do anything useful, and 
any fixes/improvements to it would be lost when the logic is moved to 
String/PerlString/PythonString/... objects.

- James