Hi Carl, at present time, when a constraint, filter, validator, ... dies we don't take care of $@, we just create a new Exception. What do you think of extending the Exception with a message function that can take that kind of message and print it later on.
The one question shall we only write it as log output (only easily possible in Catalyst environment), tell the user that the software is broke ;-) (he just gets a normal 'data invalid' message, even when there's a coding failure) or put the message next to the field like a normal error? Greets, Mario _______________________________________________ Html-widget mailing list Html-widget@lists.rawmode.org http://lists.rawmode.org/cgi-bin/mailman/listinfo/html-widget
