Re: [SMARTY-DEV] objects: one more approach

MO> Maybe another reserved parameter name: MO> MO> {$foo->bar p1="foo" p2 = "bar" wrapper=true} MO> MO> This would cause the parameter order to be important, and pass them to MO> the object in that order. Otherwise it uses the Smarty object format. just pressed send, when I thought of the following continuation from my earlier outburst... Although It would add overhead, possibly the default wrapper to user could be registered for each object. That way if I'm sharing objects with someone who only provides the 'smarty argument' interface then I can set wrapper=false for that object and the template designer is isolated from it. It's probably more likely that the interface will be consistent through one object. Nick (c)