lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]


Why would anyone want to remove asserts from release code?  So that in
a real live situation, where it actually matters, your app crashes in
mysterious ways, potentially half a day after the initial problem
would have been caught by an assert?

I've never understood this particular kind of optimisation madness.

Because you need that extra 200% of performance?

Because you're not in a position to receive error reports from users,
and act on them?

In a highly custom, consultant-installed, database-bound enterprise
application that is actively maintained by semi-intelligent IT support
personel and updated by the vendor every three months, an assert would
not slow the application down, and might lead to an improved future
version thanks to a submitted bug report.

In a console game, burned on millions of DVDs, distributed via retail
to millions of kids or other types of uncooperative users, which will
NEVER be patched, but which, on the other hand, NEEDS to hit 30 fps no
matter what, or it won't be certified by the console vendor, and where
you need every byte of available memory, even the ones taken up by
assert code, you don't need asserts in a release build.

Assen