After some CB discussion, tilly
convinced me why the open
was not such
good magic. So I devoted a separate routine to that. The filehandle still
is in the normal supersplit routine.
I personally vote for the split order of arguments, because people are more
familiar with that. I think the variable length list can be coped with by
the pop's. If that's unusual, so be it. I know that this order is mostly
not a good idea.
Moreover, you can provide a limit option now. Because there is some magic
involved, I doubled a function that doesn't try to find a limit parameter
at the end.
The code has been posted more than enough now, so I hooked it up to my
homenode. POD has been updated. Code has been tested.
I was dreaming of guitarnotes that would irritate an executive kind of guy (FZ)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||