stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Travis Vitek <vi...@roguewave.com>
Subject Re: svn commit: r616003 - /stdcxx/branches/4.2.x/tests/utilities/20.temp.buffer.cpp
Date Tue, 29 Jan 2008 07:09:11 GMT



Martin Sebor wrote:
> 
> faridz@apache.org wrote:
>> @@ -35,6 +35,7 @@
>>  
>>  #ifdef _MSC_VER
>>  #  include <climits>     // for INT_MAX
>> +#  include <crtdbg.h>    // for _CrtSetReportMode()
>>  #endif
>>  
>>  #include <rw_new.h>
> 
> Should we do this in <rw_new.h> (or new.cpp, on the first call
> to operator new or operator delete) instead?
> 
> Martin
> 

Seems that we would want to do something like this in the test driver...

  _CrtSetReportMode (_CRT_WARN, _CRTDBG_MODE_FILE);
  _CrtSetReportFile (_CRT_WARN, _CRTDBG_FILE_STDERR);

  _CrtSetReportMode (_CRT_ERROR, _CRTDBG_MODE_FILE);
  _CrtSetReportFile (_CRT_ERROR, _CRTDBG_FILE_STDERR);

  _CrtSetReportMode (_CRT_ASSERT, _CRTDBG_MODE_FILE);
  _CrtSetReportFile (_CRT_ASSERT, _CRTDBG_FILE_STDERR);

That way all tests using the driver would dump failures to the console, much
like they would on a *nix system. Is there any reason to _not_ do this?

Travis
-- 
View this message in context: http://www.nabble.com/Re%3A-svn-commit%3A-r616003----stdcxx-branches-4.2.x-tests-utilities-20.temp.buffer.cpp-tp15144552p15153678.html
Sent from the stdcxx-dev mailing list archive at Nabble.com.


Mime
View raw message