Assertions need to be replaced with real error messages for release mode compiles.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Make an app that will produce an assert.
2. Run the malformed app in release mode.

What is the expected output? What do you see instead?
Expected output:  an assertion triggered an event.

What version of the product are you using? On what operating system?
ToT on MacOSX 10.6.7.

Please provide any additional information below.
Assertions only work in Debug mode by their nature.  Real error messages to 
stderr would be preferred and exiting the program would help also.

Original issue reported on code.google.com by samueldc...@gmail.com on 31 Mar 2011 at 8:02

[GoogleCodeExporter]

I believe this issue is related to my desire to replace the current Logging 
feature in the application.  Ideally, the new logging feature will also replace 
the standard <assert.h> include capabilities with one that has more 
flexibility.  This way you could enable assertions, and other features at run 
time, instead of compile time if desired.  Further exploration into this issue 
will be made this summer.

Original comment by RyanLind...@gmail.com on 1 Apr 2011 at 6:15

[GoogleCodeExporter]

Original comment by RyanLind...@gmail.com on 14 Apr 2011 at 4:05

• Changed state: Accepted

[GoogleCodeExporter]

I am working on a new Logging system this week, hope to have this feature 
implemented as well.

Original comment by RyanLind...@gmail.com on 24 May 2011 at 4:29

• Changed state: Started
• Added labels: Maintainability, Usability

[GoogleCodeExporter]

I have just added a new logging facility to the GatorQue Engines that will soon 
replace the Assert macros.  Please review the new logging facility and let me 
know your thoughts on this, meanwhile, I will start working on replacing the 
asserts with the new logging macros as I think is appropriate.

Original comment by RyanLind...@gmail.com on 12 Jun 2011 at 2:48