>chomp() is best used for chop()s main raison d'etre, removing $/
>from a string. I say we drop chop().
So code that says
chop($k,$v)
will need to say
for ($k,$v) { s/.\z//s }
or else something like:
for ($k, $v) { substr($_, length() - 1) = '' }
I'm not sure I find either of those more legible. And they certainly
won't be faster. chop() has been around since perl1, too.
Then again, yes, people do tend to use it when they oughtn't. Hm...
---tom
- Proposal: chop() dropped Nathan Torkington
- Re: Proposal: chop() dropped Jonathan Scott Duff
- Re: Proposal: chop() dropped Tom Christiansen
- RE: Proposal: chop() dropped Al
- Re: Proposal: chop() dropped Tom Christiansen
- Re: Proposal: chop() dropped Nathan Wiger
- Re: Proposal: chop() dropped Tom Christiansen
- Re: Proposal: chop() dropped Nathan Torkington
- Re: Proposal: chop() dropped Bart Lateur
- Re: Proposal: chop() dropped skud
- Re: Proposal: chop() dropped Ed Mills
- Re: Proposal: chop() dropped Nathan Torkington
- Re: Proposal: chop() dropped Tom Christiansen
- Re: Proposal: chop() dropped Peter Scott
- Re: Proposal: chop() dropped Tom Christiansen
- Re: Proposal: chop() dropped Jonathan Scott Duff
- RE: Proposal: chop() dropped Eric Roode
