Hmmm, my understanding was that it stopped *splitting* after the limit, but it
doesn't stop "consuming" the source; rather the entire remainder is returned as
the last item in the list, even if it contains the delimiter. A bit like this:
sub split($pat, $src, $limit) {
@
> If a routine is rw, you may optionally define a single "slurpy scalar"
> (e.g., '*$value') in its signature.
A good start, but why limit the Lvalue to a scalar? A list l-value seems like a
pretty useful thing to me.
-Martin
-
I wrote:
> > Overloading "final" was Java's rather inept attempt to
> > define objects with value semantics rather than container semantics
John M. Dlugosz <[EMAIL PROTECTED]> wrote:
> Can you tell me more about that, or point to something?
Alas I can't point to anything, it's just a personal c
> -Original Message-
> From: chromatic [mailto:[EMAIL PROTECTED]
> We are trying to avoid the "java.lang.String is Final"
> problem here in various ways. One of them is not allowing
> library designers to mark things as final.
Overloading "final" was Java's rather inept attempt to def
