[Tux3] Bug fixes

[OGAWA Hirofumi]

Daniel Phillips <phillips at phunq.net> writes:

> Since assert can be defined as null to compile slightly faster and smaller
> code, this code will break.  I do sometimes write that kind of thing in unit
> tests, which will never be compiled with assert turned off, but even then...
> it is probably not a great idea.  In tux3.c, it is a (minor) bug that should
> be cleaned up, even though we have to do #define assert(expr) <nothing> to
> trigger it.

Yes, I agree. And I think it would also be good to use #include
<assert.h> with the patch of fixing assert() usage.

Thanks.
-- 
OGAWA Hirofumi <hirofumi at mail.parknet.co.jp>

_______________________________________________
Tux3 mailing list
Tux3 at tux3.org
http://mailman.tux3.org/cgi-bin/mailman/listinfo/tux3