On 10/23/07, Christopher H. Laco <[EMAIL PROTECTED]> wrote: > Personally, I always use keys, and consider _AUTO and the exposure > ERR_WRONG_PASSWORD an all out failure. I've always wanted to have a test > module that scoured source for keys and ensured they were in all l18n files.
My solution is to use Perl constants for all message ids. Given a sufficiently Perl-ish templating system, the constants can be used in both the templates and the Perl code. I accept strings too (interpreting them as the name of a Perl constant, using the usual symbolic reference evil/magic), but try pretty hard to go with constants where possible. That ensures that typos are caught at compile time. -John ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
