[dancer-users] Why do warnings cause Dancer to fail?

Stefan Hornburg (Racke) racke at linuxia.de
Tue May 6 07:23:34 BST 2014

On 05/05/2014 07:39 PM, Joel Roth wrote:
> Warren Young wrote:
>> On 5/2/2014 22:51, Joel Roth wrote:
>>> I agree that in general, it makes sense to give code more
>>> scrutiny during development.
>> I've found that most of the time, the "fatal warnings" you get when you
>> follow this practice are just silly things.  Mostly, it's complaints about
>> uninitialized variables used in strings:
>>     my $foo;
>>     ...then later...
>>     debug "Lorem ipsum $foo dolor sic amet"
>> Dancer stops the whole world, as though this has a real consequence, when it
>> really does not.  You can start feeling that Dancer has some Chicken Little
>> DNA in it.
> The latest thing I notice is that a form submitted by
> a POST request with empty fields triggers this.

Empty form fields (except of checkboxes) result in an empty string passed,
so these shouldn't cause fatal warnings.


LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team

More information about the dancer-users mailing list