Re^4: Should chomping a constant always raise an error?

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

See number 3). :)

Examine what is said, not who speaks.

Silence betokens consent.

Love the truth but pardon error.

Lingua non convalesco, consenesco et abolesco.

Comment on Re^4: Should chomping a constant always raise an error? Download Code

Replies are listed 'Best First'.
Re^5: Should chomping a constant always raise an error? by ysth (Canon) on Mar 14, 2005 at 09:11 UTC
The function I was referring to is built in, not from the CPAN module.	[reply]
Re^6: Should chomping a constant always raise an error? by BrowserUk (Patriarch) on Mar 14, 2005 at 09:44 UTC
I have an 'Internals' package, that as far as I recall, I didn't install. I assume it came with the AS distribution. It has `SetReadOnly($object) & SetReadWrite($object);` routines. I can't find any other 'Internals' that exports `svREADONLY()`. Is it documented somewhere? Examine what is said, not who speaks. Silence betokens consent. Love the truth but pardon error. Lingua non convalesco, consenesco et abolesco.	[reply] [d/l] [select]
Re^7: Should chomping a constant always raise an error? by ysth (Canon) on Mar 14, 2005 at 09:53 UTC
It is exported by perl's universal.c. It is documented by this patch :)	[reply]

In Section Seekers of Perl Wisdom