Re: [SMARTY-DEV] html_options

From: Date: Mon, 26 Feb 2007 16:39:26 +0000
Subject: Re: [SMARTY-DEV] html_options
References: 1 2  Groups: php.smarty.dev 
Request: Send a blank email to php-smarty-dev+get-2983@lists.php.net to get a copy of this message
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.

« previous php.smarty.dev (#2983) next »