[wp-hackers] load_plugin_textdomain()

Gaarai gaarai at gaarai.com
Mon Jul 28 14:09:44 GMT 2008

Just to throw my hat into the discussion, I completely agree with this 
sentiment. Making a breaking change happen later while implementing a 
confusing change to the API which will require double the work to use 
currently is baffling. Just cut the cord and force developers to update 
their stuff. Code that breaks due to lack of support will be picked up 
and fixed by the people who want to use it if there is enough interest 

- Chris

Otto wrote:
> Gotta agree, this was done wrong. A new function should have been
> created instead of adding extra parameters. With the deprecated code
> marking in 2.4 and up, plugin developers using debug mode would have
> ample warning that their function was going to be deprecated and then
> would be able to transition naturally. Instead, you've just shoved
> back the problem until 2.7 or 2.8.
> I highly recommend making a new function entirely and deprecating this
> one entirely, and doing it now, not later.
> -Otto
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list