http://qs321.pair.com?node_id=438538


in reply to Re: Should chomping a constant always raise an error?
in thread Should chomping a constant always raise an error?

That would require anyone calling the sub to tie the constants--which makes no sense at all.

It just took me by surprise that chomp died when asked to inspect a variable that was readonly. The work-arounds are myriad:

  1. The XS version of Scalar::Util has a readonly function.
  2. I could also use the eval block technique to catch the death. (Which is how the pure Perl version of Scalar::Util::readonly() does it.)
  3. The Internals package has a IsWriteProtected() function.
  4. I could use Inline::C to use the svREADONLY macro.
  5. etc.

But, as chomp has to determine if there is anything to chomp, before attempting to modify it's argument, I just expected it to make that determination before checking for readonlyness. It doesn't do it that way, so I have to do extra tests or copies myself.

I've gotten spoiled by Perl's DWIMming things like negative offsets don't die, they work backwards from the end. Same with negative subscripts; ranges that produce no values; empty lists that act correctly regardless of the context etc.

On this occasion it didn't DWIM for me.


Examine what is said, not who speaks.
Silence betokens consent.
Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco.