Fernando Cacciola [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Thanks to Gabriel we may have an is_nan() right now.
Oops!
It was Joel de Guzman who offered his is_nan() implementation.
Sorry Joel :-)
Fernando
___
Unsubscribe other
Fernando Cacciola [EMAIL PROTECTED] wrote:
Fernando Cacciola [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Thanks to Gabriel we may have an is_nan() right now.
Oops!
It was Joel de Guzman who offered his is_nan() implementation.
Sorry Joel :-)
No problem. I thought Gaby
Joel de Guzman [EMAIL PROTECTED] writes:
Alexander Nasonov [EMAIL PROTECTED] wrote:
From user point of view it's easy. Every class is described using intuitive
class-decl-like style:
void describe_Driver(descriptorDriver class_)
{
class_(Driver).derived_fromPerson()
[
Hi,
for_each seems to be unable to deal with empty lists, or lists that
are built by push_front on an empty list. However, vectors work
fine. Here is code which demonstrates the problem. Replacing list with
vector makes the code compile.
#include iostream
#include boost/static_assert.hpp
Hi Fernando (and all others)
Please find some preliminary documentation for multiindex_set
at:
http://groups.yahoo.com/group/boost/files/multiindex.zip
The documentation is far from complete, but a reasonably complete
rationale is given which hopefully will guide the reader through the
design
John Maddock wrote:
Looking at the boost regression test results, it seems that Intel on linux
defines _WCHAR_T (which is what the EDG front-end documentation specifies
for wchar_t support), so I used that as the test - should be in cvs now -
can you check that it does the right thing?
Beman Dawes [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
At 02:22 PM 7/7/2003, Rozental, Gennadiy wrote:
I could probably prohibit usage of CHECK_CLOSE with number of rounding
errors provided.
Is there any other general recommendations how to choose the tolerance
to
FP
A half-way solution is to have something like:
BOOST_CHECK_EQUAL_NUMBERS(x,y,IsEqual)
and let users specify their own Preciates.
There is BOOST_CHECK_PREDICATE
By default, the Test library could provide
a straight-forward ABSOLUTE-ERROR comparator:
By default, the Test library
Above form wouldn't should
mismatched values and this is most important.
I meant: Above form wouldn't *show* mismatched values and this is most
important.
Gennadiy.
-
___
Unsubscribe other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Hi Beman,
- Mensaje Original -
[...]
* The multiindex_set name seems awkward to me. Maybe
indexed_set or
set_index?
I don't like the name either, and would be happy if someone comes
with something better. Nevertheless, I don't think indexed_set is a
good choice: when picking up a
Thomas Wenisch wrote:
Hi,
Hi Thomas,
First of all, thanks for the report.
for_each seems to be unable to deal with empty lists, or lists that
are built by push_front on an empty list. However, vectors work
fine. Here is code which demonstrates the problem. Replacing list with
vector
Eric Friedman wrote:
Aleksey (and others),
Hi Eric,
I'm working on getting variant to compile under MSVC 6, but I've come
across what seems to be an ETI problem that needs a workaround.
However, I'm not sure what is the most appropriate way to make the fix.
The most common way to deal with
Hi,
Iteration macros did not work without some 'using' directives because it
uses functions from boots but actually without the boost:: qualifier.
E.g. BGL_FORALL_VERTICES(v,g,graph_t) did not compile unless you have using
namespace boost or using namespace boost::vertices before the invocation
Hi Csaba,
Iteration macros did not work without some 'using' directives because it
uses functions from boots but actually without the boost:: qualifier.
E.g. BGL_FORALL_VERTICES(v,g,graph_t) did not compile unless you have using
namespace boost or using namespace boost::vertices before the
Jeff Garland wrote:
In date-time there are several 'to_string' functions that provide
different ouput formats so a single 'str()' method isn't going
to be enough. As for c_str(), you can use this once you have
std::string. From my view there is no point in trying to force
fit this functionality
This framework might be interested to those who wishes to read and write
members of classes using member-names. Stuff like serialization, messaging,
automatic binding of class members with GUI/Web forms and OODBs (although
they have ODMG C++ binding).
From user point of view it's easy. Every
Jon Biggar wrote:
[...]
There is actually one case that needs a semaphore that has no reasonable
alternative in pthreads. The only pthread synchronization operation
that is asynch-reentrant safe (i.e. can be called from a signal handler)
is signaling a pthread semaphore.
There's no such
Alexander Nasonov [EMAIL PROTECTED] wrote:
From user point of view it's easy. Every class is described using intuitive
class-decl-like style:
void describe_Driver(descriptorDriver class_)
{
class_(Driver).derived_fromPerson()
[
member(Driver::licence_id, licence_id), //
I found a problem with the intel configuration for Linux.
For that compiler the macro BOOST_NO_INTRINSIC_WCHAR_T
gets defined although the compiler has an intrinsic wchar_t.
Neither _WCHAR_T_DEFINED nor _NATIVE_WCHAR_T_DEFINED is
defined on Linux. __WCHAR_TYPE__ is defined to int. Never-
19 matches
Mail list logo
