Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 3 and Version 4 of AliasFunctionReview


Ignore:
Timestamp:
Oct 31, 2008, 6:11:17 PM (15 years ago)
Author:
rlaager
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AliasFunctionReview

    v3 v4  
    11Currently, libpurple has a number of functions (in blist.h) that take a !PurpleBuddy and return some string based on one or more aliases. Some differ only slightly. Is it necessary to have all of these functions?
    22
    3 This came up because we almost certainly need to add some function to return !PurpleBuddy::alias only. The names we were picking clashed with the existing functions. Sadrul proposed _get_local_buddy_alias(). Richard agrees and suggests renaming that to _get_local_alias() in 3.0.0, replacing the currently unused (and newly deprecated) existing _get_local_alias().
     3This came up because we almost certainly need to add some function to return PurpleBuddy::alias only. The names we were picking clashed with the existing functions. Sadrul proposed _get_local_buddy_alias(). Richard agrees and suggests renaming that to _get_local_alias() in 3.0.0, replacing the currently unused (and newly deprecated) existing _get_local_alias().
    44
    55(COALESCE is borrowed from SQL to mean "return the first non-NULL item".)
     
    8585_get_local_alias = COALESCE(alias, parent->alias, name);
    8686        Unused, so deprecated just now on im.pidgin.pidgin.next.minor for 2.6.0.
    87         Richard proposes that, for 3.0.0, this return !PurpleBuddy::alias.
     87        Richard proposes that, for 3.0.0, this return PurpleBuddy::alias.
    8888
    8989_get_alias = COALESCE(alias, server_alias, parent->alias, name);
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!