Correct me if I am wrong, but shouldn't all our .c / .cpp files have these two includes: #include "lib/framework/wzglobal.h" #include "lib/framework/frame.h"
The first one we use to set platform specific defines & compiler options. The second one we use for platform specific overrides. Since that is the case, why don't all our .c / .cpp files have these? For the memory leaks, we still have quite a few of them left. astar.c, event.c, stack.c, mapgrid.c, and a few others that I have forgot about, not to mention all the strdup() leakage going on. Is it worth it to spend time trying to fix the ones that are left? The event & stack leaks are really tricky to deal with. For 2.3, we have the borg leg issue,which almost has to be a template issue of some kind, but we can't seem to replicate it, I purpose a console command "legs" that dumps the templates to a file, so people can send that file to us when this issue happens. More info here: http://developer.wz2100.net/ticket/1578 Anything else before a release? _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
