[Pidgin] #14551: API 3.0.0: PURPLE_VERSION_CHECK(2, x, 0) returns FALSE

[Pidgin]

#14551: API 3.0.0: PURPLE_VERSION_CHECK(2,x,0) returns FALSE
---------------------+------------------------------------------------------
 Reporter:  stefanb  |        Owner:           
     Type:  patch    |       Status:  pending  
Milestone:  2.10.1   |    Component:  libpurple
  Version:           |   Resolution:           
 Keywords:           |  
---------------------+------------------------------------------------------
Changes (by deryni):

  * status:  new => pending


Comment:

 The API versioning scheme was created largely *for* plugin authors. That
 is so that they can know when they do and don't need to update their code
 and to know for what versions built binaries will function.

 I'm of two minds about this specific request though as, given the major
 version incompatibility, the choices here seem to me to be "have the
 compiler (potentially) complain about things that broke only in code older
 than the checked version or have the compiler (potentially) complain about
 things broken in code newer as well and given that the plugin author is
 going to need to update their code for the new version at least a little
 forcing the removal of (now outdated) checks like that seems
 unproblematic. (Though I do see difficult with maintaining a plugin for
 multiple versions of 2.x.x and 3.x.x at the same time that this may
 potentially cause.)

-- 
Ticket URL: <http://developer.pidgin.im/ticket/14551#comment:2>
Pidgin <http://pidgin.im>
Pidgin