comparison libpurple/protocols/sametime/sametime.c @ 21317:84925e6055bc

Use distinct variables for the result of g_strerror (which is const) and a g_strdup_printf (which is not), squashing a warning in sametime.
author Will Thompson <will.thompson@collabora.co.uk>
date Sun, 11 Nov 2007 14:10:06 +0000
parents 6de09629f091
children 1ce05db42eb3
comparison
equal deleted inserted replaced
21316:d0b16c09c2c4 21317:84925e6055bc
1700 if(! ret) { 1700 if(! ret) {
1701 DEBUG_INFO("connection reset\n"); 1701 DEBUG_INFO("connection reset\n");
1702 purple_connection_error(pd->gc, _("Connection reset")); 1702 purple_connection_error(pd->gc, _("Connection reset"));
1703 1703
1704 } else if(ret < 0) { 1704 } else if(ret < 0) {
1705 char *msg = g_strerror(err); 1705 const gchar *err_str = g_strerror(err);
1706 1706 char *msg = NULL;
1707 DEBUG_INFO("error in read callback: %s\n", msg); 1707
1708 1708 DEBUG_INFO("error in read callback: %s\n", err_str);
1709 msg = g_strdup_printf(_("Error reading from socket: %s"), msg); 1709
1710 msg = g_strdup_printf(_("Error reading from socket: %s"), err_str);
1710 purple_connection_error(pd->gc, msg); 1711 purple_connection_error(pd->gc, msg);
1711 g_free(msg); 1712 g_free(msg);
1712 } 1713 }
1713 } 1714 }
1714 1715