Mercurial > pidgin.yaz
view PROGRAMMING_NOTES @ 4200:c8fb43808a4b
[gaim-migrate @ 4431]
I try to look at it like this:
At least now I know a little more about va_args.
So when you pass stuff through "...", gcc promotes the argument to an
integer. So passing fu16_t because 4 bytes instead of 2. Then when
using va_args, you have to use a type that is 4 bytes instead of 2.
I guess va_args is different in gcc 2, in that, if you give it a 2 byte
type, it will get 4 bytes anyway. Either that, or gcc2 doesn't promote
stuff to 4 bytes when passed through ....
Anyway, sorry to all gcc3.x users. This patch just fixes a little bit
of whitespace stuff, again, for no real reason.
committer: Tailor Script <tailor@pidgin.im>
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Sat, 04 Jan 2003 19:41:07 +0000 |
parents | e074172f4a41 |
children | 59ff9d0b7b85 |
line wrap: on
line source
Notes on keeping GAIM OS independant ------------------------------------ General ------- - Use G_DIR_SEPARATOR_S and G_DIR_SEPARATOR for paths - Use g_getenv, g_snprintf, g_vsnprintf - Use gaim_home_dir instead of g_get_home_dir or g_getenv("HOME") - Make sure when including win32dep.h that it is the last header to be included. Paths ----- - DATADIR, LOCALEDIR & LIBDIR are defined in wingaim as functions. Doing the following will therefore break the windows build: printf("File in DATADIR is: %s\n", DATADIR G_DIR_SEPARATOR_S "pic.png"); it should be: printf("File in DATADIR is: %s%s%s\n", DATADIR, G_DIR_SEPARATOR_S, "pic.png"); PLUGINS & PROTOS ---------------- - G_MODULE_EXPORT all functions which are to be accessed from outside the scope of its "dll" or "so". (E.G. gaim_plugin_init) - G_MODULE_IMPORT all global variables which are located outside your dynamic library. (E.G. connections) (Not doing this will cause "Memory Access Violations" in Win32)