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.
- Timestamp:
-
Oct 31, 2008, 6:10:36 PM (15 years ago)
- Author:
-
rlaager
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v2
|
v3
|
|
1 | 1 | Currently, 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? |
2 | 2 | |
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: |
| 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(). |
4 | 4 | |
5 | 5 | (COALESCE is borrowed from SQL to mean "return the first non-NULL item".) |
… |
… |
|
85 | 85 | _get_local_alias = COALESCE(alias, parent->alias, name); |
86 | 86 | 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 | 88 | |
88 | 89 | _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!