Re: Testing Program Question
On Feb 12, 5:22 am, Immortal Nephi <Immortal_Ne...@hotmail.com> wrote:
I am unable to find good documentation which talks about debug
macro.
You mean NDEBUG? At the language level, all it commands is
assert (but there's nothing to stop you from using it yourself).
The exception may be used for testing purpose.
/* C Code */
void foo( int x )
{
#if _DEBUG
if( x > 10 )
std::cerr << "x value must not be greater than 10." << std::endl;
Just a nit, but in C++, the characters for delimiting a string
are ". And nothing else, even if it looks like a ".
And there is no _DEBUG macro defined in the language. What it
does is up to you and the implementation. (Mainly the
implementation, since it's in the implementation namespace.)
#endif // _DEBUG
// Run normal execution
}
/* C++ Code */
static const bool TESTING = true;
void foo( int x )
{
if( TESTING )
if( x > 10 )
std::cerr << "x value must not be greater than 10." << std::endl;
// Run normal execution
}
Excuse me, but there's nothing C vs. C++ here. Both of the
programs are C++. And the debug macro is generally one of the
rare things you want to be a macro, so you can set or reset it
from the command line.
C++ Compiler has the _DEBUG option.
The C++ compiler will allow pretty much any macro you care to
define.
_DEBUG option is turned off if release mode is active and any
_DEBUG macro blocks are ignored.
It's not an "option". It's a macro, that you define or not, as
you like. And there's no such thing as "modes" with regards to
C++.
I have no idea how C++ does not use _DEBUG macro. I wonder
that TESTING condition will be removed if optimization is
turned on when release mode is active.
Probably, but the content still has to be compilable C++.
Please tell me more how cerr and clog are useful.
Fundamentally, they're just different pre-defined streams.
Classically, cerr wouldn't get redirected, even when cout was,
and by default, the output of cerr is unit buffered, but that's
about it.
I do not want to see error messages in the console window. I
want to see error message in window dialog when Microsoft
Visual C++ .NET 9.0 triggers assertion request.
So you'll have to implement something else. If you're not using
cout, then cerr probably isn't much use either.
I may not need exception because step by step debugging
procedure is simpler than throw, try, and catch keywords.
It's not clear what types of errors you have in mind.
Programming errors are generally best handled by immediately
aborting, at least in production code, at least in most
application domains. Depending on circumstances, other errors
are best handled with exceptions or return codes.
--
James Kanze