If a string is missing a value, that is an indication of a potential bug. The warning tells me that what I expected is not what I got. Either I have over looked someplace where a default should be set, or the incoming data is deficient (the User didn't fill in a field on the form, the database is missing a value, etc.) As a matter of defensive programming, I want to know that a value was missing, so I can run the bug to earth and fix it. And also determine why my test harness missed it. (The Spec said that User-ID-Alias is a required field, so why is it blank in the DB?)
Now, whether the end-user of my code sees the warning is another matter. I write errors and warning to logs that I can check later. For code going into production for the first time, the first few days of those logs can be very enlightening (or horrifying....).
----
I Go Back to Sleep, Now.
OGB
In reply to Re: Do people find warning for undef with string compare useful?
by Old_Gray_Bear
in thread Do people find warning for undef with string compare useful?
by perl-diddler
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |