Posted by Joe Stump on 06/18/05 02:10

> Never-the-less, I take exception to one statement: Smarty is not
> broken
> for PHP5. It simply doesn't support everything that PHP5 can do which
> is very different than being broken.

By this same rational IE's support for CSS isn't broken, it just
doesn't support everything that CSS can do.

--Joe


>
> Best,
> xo boots
>
> --- Joe Stump <joe@joestump.net> wrote:
>
>> Wait. I'm confused. {$foo->bar()->display()} would break backwards
>> compatibility, but rewriting Smarty for PHP5 wouldn't? Plus, how
>> would allowing for {$foo->bar()->display()} break Smarty's ability to
>>
>> run on PHP4? It would only break that template's ability to run on
>> PHP4.
>>
>> I see a few solutions here:
>>
>> 1.) Just make it so Smarty can handle PHP5 dereferencing. This would,
>> of course, break the templates (again, not Smarty itself), if they
>> were ran under PHP4.
>>
>> 2.) Have two versions of Smarty (2.x is PHP4, 3.x is PHP5). I'm sure
>> this is probably already in progress to some degree (PHPUnit and
>> phpDocumentor both have dual versions out right now).
>>
>> The fact still remains - Smarty is broken under certain circumstances
>> for PHP5. To get around this problem you will have to do the
>> following:
>>
>> {assign var="bar" value=$foo->getClass()}
>> {$bar->display()}
>>
>> --Joe
>>
>
>

[Back to original message]