Opened at 2012-07-06T20:55:24Z
Closed at 2012-07-06T21:25:34Z
#974 closed enhancement (alreadydoingthat)
use g_ascii_str* functions instead of g_str*
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | BitlBee | Version: | 3.0.5 |
| Keywords: | Cc: | ||
| IRC client+version: | Client-independent | Operating System: | Public server |
| OS version/distro: |
Description
The g_ascii_str* functions were introduced as a replacement for the less appropriately named g_str* functions. As of glib 2.2 (released 10 years ago), the g_str* functions are marked as deprecated and should not be used. To avoid potential future issues with compilation, replace all instances of these functions with the recommended new equivalents. This affects usage of g_strncasecmp as well.
Given the elapsed time frame here, it seems unlikely that these functions will ever go away, but this is an easy way to get rid of a lot of compiler warnings, making other warnings/errors stand out more.
The attached patch was generated from a bzr checkout.
Attachments (1)
Change History (4)
Changed at 2012-07-06T20:55:41Z by
| Attachment: | use_g_ascii_str_functions.patch added |
|---|
comment:1 Changed at 2012-07-06T20:57:46Z by
comment:2 Changed at 2012-07-06T21:04:47Z by
Apparently it was -- intriguing way of solving it, I suppose. You can mark this invalid -- apologies for the noise.
comment:3 Changed at 2012-07-06T21:25:34Z by
| Resolution: | → alreadydoingthat |
|---|---|
| Status: | new → closed |
Heh, yeah, it's definitely a hack.
But when library authors do stupid backward-incompatible stuff I will hack around it in ways that take the least effort. This works perfectly. :-)
Which one, something older than changeset:devel,911?