Changeset 04026d4
- Timestamp:
- 2006-07-15T17:26:13Z (18 years ago)
- Branches:
- master
- Children:
- 0aaca60
- Parents:
- 89a1809
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
account.c
r89a1809 r04026d4 52 52 s->flags |= ACC_SET_NOSAVE; 53 53 54 s = set_add( &a->set, "auto_reconnect", "true", set_eval_ account, a );54 s = set_add( &a->set, "auto_reconnect", "true", set_eval_bool, a ); 55 55 56 56 s = set_add( &a->set, "password", NULL, set_eval_account, a ); -
irc.c
r89a1809 r04026d4 624 624 char namelist[385] = ""; 625 625 struct conversation *c = NULL; 626 char *ops = set_getstr( irc, "ops" );626 char *ops = set_getstr( &irc->set, "ops" ); 627 627 628 628 /* RFCs say there is no error reply allowed on NAMES, so when the -
lib/events_glib.c
r89a1809 r04026d4 122 122 gint b_timeout_add(gint timeout, b_event_handler func, gpointer data) 123 123 { 124 gint st = g_timeout_add(timeout, func, data); 124 /* GSourceFunc and the BitlBee event handler function aren't 125 really the same, but they're "compatible". ;-) It will do 126 for now, BitlBee only looks at the "data" argument. */ 127 gint st = g_timeout_add(timeout, (GSourceFunc) func, data); 125 128 126 129 event_debug( "b_timeout_add( %d, %d, %d ) = %d\n", timeout, func, data, st ); -
lib/events_libevent.c
r89a1809 r04026d4 101 101 102 102 /* Since the called function might cancel this handler already 103 (which free()s b_ev , we have to remember the ID here. */103 (which free()s b_ev), we have to remember the ID here. */ 104 104 id = b_ev->id; 105 105
Note: See TracChangeset
for help on using the changeset viewer.