Deprecating registerObject()

[Rodney Rehm]

Uwe and I have been discussion the relevance of registerObject(). In light of developing Smarty 3.2 we've been discussing if this feature (we just can't see useful) might be deprecated.

This is a call to tell us if (and why) you're using registered objects (or know of anyone / anything doing so). In case of a meager response we are willing to move registerObject() to SmartyBC (to accompany {php} et al).

(corresponding post in the forum)

Regards,
Rod

[Rodney Rehm]

Is nobody using the registerObject() feature? really?

[aurelien gerits]

Hello, what will the effect of putting registerObject depreciated?
Does this will affect the rest of the engine?
Best regards

2012/2/16 Rodney Rehm <rodne...@medialize.de>

Is nobody using the registerObject() feature? really?

--
You received this message because you are subscribed to the Google Groups "Smarty Developers" group.

To view this discussion on the web visit https://groups.google.com/d/msg/smarty-developers/-/mjU-wfkuhEMJ.

To post to this group, send email to smarty-d...@googlegroups.com.
To unsubscribe from this group, send email to smarty-develop...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/smarty-developers?hl=en.

[Rodney Rehm]

If we move to deprecate registerObject(), it will only be available through SmartyBC (the backward compatibility layer). That allows us to remove code from the core and allows us to stop maintaining that feature, as it will eventually be dropped completely.

This will affect only calls to registerObject() and their template counter-part syntax {$object->method some="argument" more="parameters"}. all registerObject ever did was allow an object method being invoked like a smarty plugin. This, of course, meant the object's methods had to have the same signature the smarty plugins require.

We've never used this feature ourselves and have never encountered any real use of it in the wild. This is why we're asking if we can move to deprecate it. No need to maintain functionality that nobody uses. Especially if it can be done in another (better) way.

[Emmanuel Simond]

Please, KISS ! 

& Thanks for your Smarty Templates Engine, please keep it simple and FAST please

Have a Great Day

Emmanuel

[Jeff MacDonald]

On Thursday, February 16, 2012 03:43:21 AM Rodney Rehm wrote:
> If we move to deprecate registerObject(), it will only be available through
> SmartyBC (the backward compatibility layer). That allows us to remove code
> from the core and allows us to stop maintaining that feature, as it will
> eventually be dropped completely.
>

+1 to deprecate and then remove completely in the near future.

Regards,
J

[Karel S.]

Never used this method, +1 to deprecate.