[prev in list] [next in list] [prev in thread] [next in thread] 

List:       smarty-dev
Subject:    Re: [SMARTY-DEV] html_options
From:       Monte Ohrt <monte () ohrt ! com>
Date:       2007-02-26 16:39:26
Message-ID: 45E30D3E.6030501 () ohrt ! com
[Download RAW message or body]

Danilo Buerger wrote:
>
>>
>> Personally, I think the point is moot. Whether or not you can 
>> generally use
>> true/false as array keys, AFAIK, one can never get the PHP values 
>> true or false
>> back from a form post. In that light, one has no business specifying 
>> them when
>> they really mean to specify 0 or 1, not?
>>
>> boots
>>
>
> Well it could be for semantic reasons that someone wants to have 
> something like this:
>
> $smarty->assign('options', array(true => 'Yes', false => 'No'));
> $smarty->assign('select_yes_by_default', false);
>

If it can be addressed with no BC breakage, it doesn't bother me. 
Otherwise, I don't think that is important of a concern. We are 
splitting hairs here, these are boolean values getting passed to 
{html_options} option values, an HTML-specific function which won't 
preserve variable types anyways, as boots mentioned.

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

[prev in list] [next in list] [prev in thread] [next in thread]