APIs change in incompatible ways sometimes. When it's avoidable, that's great. Andrew seems to indicate that in this case, it wasn't possible to keep the hooks identical to how they were. That's why its best to keep extensions in svn so developers can easily spot and fix issues like this when they arise.
-Chad
On Fri, Apr 24, 2009 at 6:50 PM, Brian Brian.Mingus@colorado.edu wrote:
Whatever happened to object-oriented programming and abstraction? Why can't you define and provide a consistent API?
On Fri, Apr 24, 2009 at 3:06 PM, Aryeh Gregor <Simetrical+wikilist@gmail.comSimetrical%2Bwikilist@gmail.com
wrote:
On Fri, Apr 24, 2009 at 4:59 PM, Brian Brian.Mingus@colorado.edu wrote:
I am just hoping to prevent a repeat of ParserPP.
A *lot* more extensions use parser-related stuff than preferences. In any event, the upheaval of ParserPP was probably necessary given what it sought to achieve. That sort of thing happens from time to time -- it's not feasible for extensions with access to so many hooks and methods to just work forever.
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l