On 1/10/07, Peter Scott <[EMAIL PROTECTED]> wrote:
On Wed, 10 Jan 2007 08:32:26 -0500, Muttley Meen wrote: > On 1/10/07, Peter Scott <[EMAIL PROTECTED]> wrote: >> On Wed, 10 Jan 2007 07:37:24 -0500, Muttley Meen wrote: >> > I have the code: >> > $SIG{__WARN__} = sub { print $_[0]; } ; >> >> perldoc -f die >> >> (perldoc -f warn should probably be clearer on this.) >> > Already did that :)Which one? perldoc -f die explains what you are seeing. I already submitted a patch for perldoc -f warn to make it clearer that you need to look there.
this was my problem. And I presumed that a perldoc result is somewhat similar to a `man` command. Meaning it has references. But I was wrong. The only reference to `die` is : "Produces a message on STDERR just like "die", but doesn't exit or throw an exception." I guess a line mentioning the "\n" trick would be more straight forward. Now back on subject. The '\n' trick to get rid of the 'at line' suffix is is not an expected behaviour. What I'm expecting to see is : if I rewrite __WARN__, then do it my way, don't append anything else; of course this might have some explanation I'm not aware of. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
