- Original Message -
From: Rozental, Gennadiy [EMAIL PROTECTED]
To: 'Boost mailing list' [EMAIL PROTECTED]
Sent: Tuesday, November 26, 2002 7:13 PM
Subject: RE: [boost] Factoring out Test Library wrapstrstream
(3) fully included
The problem with this is that I put the burden
The problem is that BCC, by default, uses an 'intrinsic'
version of strcmp
which is not a real function thus it is not located in std.
Declaring strcmp
inside std doesn't help.
The workaround is to either use unqualified calls to strcmp
or to disable
its intrinsic version. My patch does
- Original Message -
From: Rozental, Gennadiy [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, November 25, 2002 4:17 AM
Subject: RE: [boost] Factoring out Test Library wrapstrstream
My tests are already arranged in a way that 'test/minimal.hpp' offers
too
little functionality
(3) fully included
The problem with this is that I put the burden of doing so to
the user.
I do not get it. In this case you are the user (of Boost.Test library). To
use fully included version you are using
#include boost/test/included/test_exec_monitor.hpp
And that's it. No need for
My tests are already arranged in a way that 'test/minimal.hpp' offers too
little functionality while a whole test framework, such as
test_execution_monitor or unit_test_framework requires me link or
include too many translation units.
Well currently Boost.Test propose three configuration:
1.