On Thu, 5 Oct 2000, Dana C. Chandler III wrote: > In my limited experience, it is Perl in general that treats the value 0, > in a query string as the empty string. In all of the scripts I have > written, if 0 is possible as a param value, I have to explicity check > for 0. This is only the case when you're going: if ($r->param('name')) { # do something } if its a zero then you should expect to be bitten in the ass by that one. However I do assume that there's similar code going on somewhere to turn the zero into undef. -- <Matt/> ** Director and CTO ** ** AxKit.com Ltd ** ** XML Application Serving ** ** http://axkit.org ** ** XSLT, XPathScript, XSP ** ** Personal Web Site: http://sergeant.org/ **
- Re: HTML Template Comparison Sheet ETA G.W. Haywood
- Re: HTML Template Comparison Sheet ETA Drew Taylor
- Re: HTML Template Comparison Sheet ETA G.W. Haywood
- HTML Template Systems Billy Donahue
- Re: HTML Template Systems G.W. Haywood
- Re: HTML Template Comparison Sheet ETA Nelson Correa de Toledo Ferraz
- Re: HTML Template Comparison Sheet ETA Sapphire Software
- Apache::Request and parameters = 0 John Reid
- Re: Apache::Request and parameters = 0 Matt Sergeant
- Re: Apache::Request and parameters = 0 Dana C. Chandler III
- Re: Apache::Request and parameters = 0 Matt Sergeant
- Re: Apache::Request and parameters = 0 John Reid
- Re: Apache::Request and parameters = 0 Dana C. Chandler III
- Re: Apache::Request and parameters = 0 Matt Sergeant
- Re: HTML Template Comparison Sheet ETA Andrew Ford
- Re: HTML Template Comparison Sheet ETA Paul J. Lucas
- Re: HTML Template Comparison Sheet ETA Perrin Harkins
- Re: HTML Template Comparison Sheet ETA Paul J. Lucas
- Re: HTML Template Comparison Sheet ETA Billy Donahue
- Re: HTML Template Comparison Sheet ETA Paul J. Lucas
- Re: HTML Template Comparison Sheet ETA Eric L. Brine