comment on

Mostly, because splice (and slice syntax) allow complete control over where to start and how many.

And library routine use those terms combined with map is going to have to be -- or at least feel the pressure to be -- equally flexible.

And a) that flexibility would have a disastrous affect on both usability & efficiency for the simple case; b) I've never encountered a need for that flexibility; where the simple case can (and has for me in recent months), crop up very frequently.

Also, splice modifies array, this just provides snapshots.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^5: Want for a name? (Final thoughts; strong feelings; votes?) by BrowserUk
in thread Want for a name? by BrowserUk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks