Gene E. Bloch wrote:
On Sat, 16 Jun 2012 18:31:14 -0400, Paul wrote:

The "assert" is in source code module "wincore.cpp". Wincore.cpp
would be one of many files, compiled and linked together to
make GUI.exe.

My guess would be, the code attempts to open "text file Language.xml"
in the install folder, the file is missing, the file opening call
returns an error code, and rather than use a proper error handler,
they check with an "assert", which is silly and sloppy.

In my experience and practice, and assert will never be triggered unless
there's a bug in the program.

But I wasn't trying to teach programming practice to Allen Drake, I was
trying to help him stop some programs from running.


Well, my comment was to point out, that a "finished" program,
shouldn't be throwing asserts at users.

What was done here, was an abuse of an assert. Files come and
go, and if a file is missing, should be handled with a dialog
box, and a suggestion as to how to repair it. Like "put back
my configuration file, you oaf" or something similarly friendly :-)

For examples of helpful dialogs, I recommend reviewing the
dialogs provided by the "Imgburn" program. Always good for a
laugh, as well as the loud sound effects used when the program
is finished. That's an example of some over-the-top programming.
At least I haven't seen any "asserts" leak out of that program.
Every event is handled sarcastically and with precision.

Paul