Hi, At the moment we use wassert which is mainly a wrapper to assert. But it has an option to be used for platforms which don't support assert. Since we also have code which uses the normal asserts I assume the code for wassert to be obsolete. If there are no objections I'll remove wassert.hpp and wassert.cpp and convert the code to use assert instead of wassert.
Related to that we have quite some code that uses asserts on data transferred from WML. For some reason our builds are compiled with assertions still working, once we get a platform which doesn't we might get some weird bug reports. I added WML_ASSERT [1] which can test a condition but can also have a message to give hints to the user what went wrong. When this assert is triggered it should be catch at game level (or before) so we can show an error and go back to the titlescreen. This avoids terminations due to asserts, which users see as crashes. I'll look into converting the existing code to use this kind of assert and also look at which asserts should be a runtime check. Regards, Mark de Wever aka Mordante/SkeletonCrew [1] https://mail.gna.org/public/wesnoth-commits/2007-12/msg00024.html _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
