Re: [SMARTY] Re: [SMARTY-DEV] Re: [SMARTY] modifier_string_format in 2.5.0-RC1
| From: | Paul Lockaby | Date: | Thu, 06 Mar 2003 22:12:55 +0000 |
| Subject: | Re: [SMARTY] Re: [SMARTY-DEV] Re: [SMARTY] modifier_string_format in 2.5.0-RC1 | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.smarty.dev |
| Request: | Send a blank email to php-smarty-dev+get-907@lists.php.net to get a copy of this message | ||
messju mohr wrote:
On Thu, Mar 06, 2003 at 03:55:47PM -0600, Monte Ohrt wrote:Hmm, didn't realize that. Excuse me for a moment for being dumb.Hmm, I'm not the originating author of the modifier structure, but I'll take a guess :-) Function attributes have name/value pairs so an associative array makes sense, and order is not an issue. OTOH, modifier parameters are only values so their order is important. I suppose they could have been passed as an enumerated array of values, that way the second parameter can be the smarty object much the same as functions are. But then your modifier would need to know what each value of $params[0], $params[1], etc. are for without an intuitive name.one can use func_get_args() to write modifiers with a variable number arguments, so there is no need to break bc for this.
but having &$smarty available in modifiers would be worth it for me... :)~Paul