Re: Handling TRUE,FALSE,NULL,ON,OFF, etc

On Tue, 06 Apr 2004, Mark Rogers wrote:
> Consider:
>     {blockfunc somevar=true othervar=TRUE}
>     ..
>     {/blockfunc}
> 
> At present, $somevar will be set to boolean(TRUE) while $othervar gets set
> to string("TRUE"). (It's within a block function I came across this, I
> assume it affects other places too?)
> 
> Clearly (??) this is wrong, and easy to fix in
> Smarty_Comiler::_parse_attrs() by making the two regexps case insensitive
> (case 2 of switch). Additionally, the check for "null" should accomodate
> "NULL".

Why? What is the predominant reason for wanting TRUE to resolve to
boolean? What is wrong with case-sensitivity?

- Andrei

-- 
Smarty Development Mailing List (http://smarty.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php