[Warzone-dev] SVN broken

2006-11-04 Thread Gerard Krol
This change: Revision 450 - (view) (download) (as text) - [select for diffs] Modified Sat Nov 4 02:11:26 2006 CET (15 hours, 53 minutes ago) by devurandom File length: 9752 byte(s) Diff to previous 389 - Droped a lot of (nearly) unused types from lib/framework/types.h - Remove lots of unused

[Warzone-dev] Patches (2 segfaults + 3 minor)

2006-11-04 Thread Thomas Rast
Hello everyone! First off allow me to thank you for the work so far. I especially like the linux port! :-) Attached are a few small patches. All of them are against r450, which is HEAD as of this writing. In order of severity: * charon-sound-id-segfault.diff This one is not reproducible.

Re: [Warzone-dev] Patches (2 segfaults + 3 minor)

2006-11-04 Thread Thomas Rast
Sorry for the spam, but... Attached are a few small patches. The signature is broken, probably due to a bug in KMail. If you want, I can re-send, but the whole routine is a bit pointless anyway as you can't verify my public key. - Thomas -- GPG key ID 'BB66CCFD' available from

Re: [Warzone-dev] Patches (2 segfaults + 3 minor)

2006-11-04 Thread Dennis Schridde
Am Samstag, 4. November 2006 19:25 schrieb Thomas Rast: Sorry for the spam, but... Attached are a few small patches. The signature is broken, probably due to a bug in KMail. If you want, I can re-send, but the whole routine is a bit pointless anyway as you can't verify my public key. I

Re: [Warzone-dev] Patches (2 segfaults + 3 minor)

2006-11-04 Thread Dennis Schridde
Am Samstag, 4. November 2006 18:45 schrieb Thomas Rast: Hello everyone! Hello Thomas, nice to see you here! * charon-decl-fix.diff mingw32-gcc chokes on the difference between SDWORD and DWORD. (My GCC 4.0.3 on Linux didn't, however.) DWORD is defined to SDWORD on non WIN32 only, it seems

Re: [Warzone-dev] More patches for warnings

2006-11-04 Thread vs2k5
On Thu, 02 Nov 2006 16:27:51 -0500 Troman [EMAIL PROTECTED] wrote: It is a cleaner approach, but for me it is more intuitively to use MALLOC since already the name implies that malloc functionality will be used at some point. And these 2 new macros will not replace all occurances of MALLOC,