changeset
jabber: did someone say something about the end of the struct?
Sat, 07 Nov 2009 04:41:04 +0000
- author
- Paul Aurich <darkrain42@pidgin.im>
- date
- Sat, 07 Nov 2009 04:41:04 +0000
- changeset 28840
- 0921099465ec
- parent 28839
- 16ed31feeabf
- child 28841
- 6b9568572bcb
- child 28855
- c5bc85f9c00e
- child 29642
- ef61075f9587
jabber: did someone say something about the end of the struct?
Not sure what the original thinking was there (other than to have JabberStream
be part of the public API?), but this is no longer accurate.
| libpurple/protocols/jabber/jabber.h | file | annotate | diff | comparison | revisions |
--- a/libpurple/protocols/jabber/jabber.h Sat Nov 07 03:45:13 2009 +0000 +++ b/libpurple/protocols/jabber/jabber.h Sat Nov 07 04:41:04 2009 +0000 @@ -193,25 +193,16 @@ char *serverFQDN; - /* OK, this stays at the end of the struct, so plugins can depend - * on the rest of the stuff being in the right place - */ #ifdef HAVE_CYRUS_SASL sasl_conn_t *sasl; sasl_callback_t *sasl_cb; -#else /* keep the struct the same size */ - void *sasl; - void *sasl_cb; -#endif - /* did someone say something about the end of the struct? */ -#ifdef HAVE_CYRUS_SASL const char *current_mech; int auth_fail_count; -#endif int sasl_state; int sasl_maxbuf; GString *sasl_mechs; +#endif gboolean unregistration; PurpleAccountUnregistrationCb unregistration_cb;
