Imagine the following scenario: your script contains a doiuble-quotish
40 line here-doc, with a bunch of variables in it. Unforetunately, you
forgot to set one, and you get the not so helpful complaint:

        use of unitialized value at line xxx

where xxx is the line number for the line that contains the "<<" for the
here doc. Now, what variable was it? Happy hunting!

Imagine that you could easily override the conversion of undef() into a
string, so that when stringified it returns something like "#UNDEF#"
instead of just an empty string. That would make debugging far more
easy: take a look at the output, and search for this sentinel string.

I must admit that apart from easy debugging, this feature would hardly
serve any other practical purpose.

-- 
        Bart.

Reply via email to