Re: [SMARTY-DEV] objects: one more approach
| From: | Monte Ohrt | Date: | Wed, 15 Jan 2003 17:28:20 +0000 |
| Subject: | Re: [SMARTY-DEV] objects: one more approach | ||
| References: | 1 2 | Groups: | php.smarty.dev |
| Request: | Send a blank email to php-smarty-dev+get-546@lists.php.net to get a copy of this message | ||
I have a prototype working. But a problem exists with registering
objects. How would you register them?
{$foo->bar p1="foo" p2="bar"}
{$zeebeefoo->bar p1="foo" p2="bar"}
{$blah.bleh->zeebeefoo->bar p1="foo" p2="bar"}
How are these going to get registered? Maybe we don't do object
registration and we stick to not allowing access to private methods when
security is enabled. Any other access restrictions are handled by the
object?
There is also the issue with identifying property vs. method. At compile
time the compiler doesn't know which is which. Should it send it to a
function that figures it out at runtime? I'd rather be able to
distinguish this at compile time and keep the compiled code faster.
Monte
On Wed, 2003-01-15 at 10:48, loic d'Anterroches wrote:
> Hello,
>
> I vote also for:
> > $foo->bar(array('p1' => "foo", 'p2' => $bar),
> > $this);
>
> loic
>
> --
> +++ GMX - Mail, Messaging & more http://www.gmx.net +++
> NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!
--
Monte Ohrt <monte@ispi.net>