Re: chop/chomp bind too tightly

You'd find that pos() and vec() behave like chop() and chomp()... except that they're supposed to!

_____________________________________________________
Jeff[japhy]Pinyan: Perl, regex, and perl hacker.
s++=END;++y(;-P)}y js++=;shajsj<++y(p-q)}?print:??;

Comment on Re: chop/chomp bind too tightly

Replies are listed 'Best First'.
(tye)Re: chop/chomp bind too tightly by tye (Sage) on Nov 15, 2001 at 00:04 UTC
Neither pos nor vec are "list operators". I say this because I don't see "pos LIST" nor "vec LIST" in the "Synopsis" section of their respective documentation entries. I also checked `perl -e "print prototype('CORE::chomp')"` for several of the items, but that appears to be a rather imperfect test. Perhaps it is the "chop VARIABLE" and "chomp VARIABLE" entries in their synopsis sections that (indirectly) explain this behavior? - tye (but my friends call me "Tye")	[reply] [d/l]

Replies are listed 'Best First'.

(tye)Re: chop/chomp bind too tightly
by tye (Sage) on Nov 15, 2001 at 00:04 UTC

Neither pos nor vec are "list operators". I say this because I don't see "pos LIST" nor "vec LIST" in the "Synopsis" section of their respective documentation entries.

I also checked perl -e "print prototype('CORE::chomp')" for several of the items, but that appears to be a rather imperfect test.

Perhaps it is the "chop VARIABLE" and "chomp VARIABLE" entries in their synopsis sections that (indirectly) explain this behavior?

tye

[reply]
[d/l]