comparison libpurple/connection.c @ 17563:44393d3e0c3b

Don't use g_critical to report that purple_connection_error was called with text == NULL
author Stu Tomlinson <stu@nosnilmot.com>
date Sat, 09 Jun 2007 14:11:39 +0000
parents 10f175539cfe
children bb2e5f6ff2b4
comparison
equal deleted inserted replaced
17562:6f54b1e84610 17563:44393d3e0c3b
434 PurpleConnectionUiOps *ops; 434 PurpleConnectionUiOps *ops;
435 435
436 g_return_if_fail(gc != NULL); 436 g_return_if_fail(gc != NULL);
437 437
438 if (text == NULL) { 438 if (text == NULL) {
439 g_critical("purple_connection_error: check `text != NULL' failed"); 439 purple_debug_error("connection", "purple_connection_error: check `text != NULL' failed");
440 text = _("Unknown error"); 440 text = _("Unknown error");
441 } 441 }
442 442
443 /* If we've already got one error, we don't need any more */ 443 /* If we've already got one error, we don't need any more */
444 if (gc->disconnect_timeout) 444 if (gc->disconnect_timeout)