[Pidgin] #9253: pidgin_blist_destroy never called, ignores its argument

Pidgin trac at pidgin.im
Sun Jul 12 02:05:24 EDT 2009


#9253: pidgin_blist_destroy never called, ignores its argument
----------------------+-----------------------------------------------------
 Reporter:  andrikos  |        Owner:  darkrain42  
     Type:  defect    |       Status:  new         
Milestone:  3.0.0     |    Component:  pidgin (gtk)
  Version:  2.5.6     |   Resolution:              
 Keywords:            |  
----------------------+-----------------------------------------------------

Comment(by darkrain42 at pidgin.im):

 (In [90138fae4d2350d166f730736ecea9ee8e20ecdb]):[[BR]]
 Free the buddy list data some more at shutdown and some deprecations.

 I think these deprecations are reasonable. Basically, purple_blist_init
 should create a PurpleBuddyList*, so each UI doesn't need to do that.
 The UI data for the PurpleBuddyList is more tightly coupled with
 the PurpleBuddyList and purple_blist_destroy is called in
 purple_blist_uninit (and is fully cleaned up now).

 As libpurple works currently, I believe it's not really possible to have
 multiple PurpleBuddyLists around (blist.c relies on a single global
 variable) and when it was discussed on the mailing list a few months ago,
 nobody was using it as such.

 Refs #9253 (going to milestone 3.0.0 it).

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


More information about the Tracker mailing list