> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Saturday, June 14, 2003 4:32 PM
...
> In article <[EMAIL PROTECTED]>,
> Beman Dawes <[EMAIL PROTECTED]> wrote:
> >I've been working with Greg Comeau for the last couple of
> weeks trying
> >to
> >resolve v
>
>Subject: Re: [boost] BOOST_STATIC_WARNING ?
> From: "John Maddock" <[EMAIL PROTECTED]>
> Date: Sun, 15 Jun 2003 12:55:15 +0100
> To: "Boost mailing list" <[EMAIL PROTECTED]>
>
>> I find BOOST_STATIC_ASSERT(...) extremely useful.
>>
>> I would also find BOOST_STATIC_WARNING(...) extremel
>
>BOOST_STATIC_WARNING( "we're in boost_file.hpp")
Ok, the example was a little bit stupid, but you get the point.
(should have somehow been BOOST_STATIC_WARNING(WCHAR_MIN >= 0);)
By the way, why not extend the BOOST_STATIC_ASSERT a la Andrei:
BOOST_STATIC_ASSERT( sizeof(type) > 1, type_should_c
I made attempt to use boost's filesystem on Novell NetWare (Metrowerks
CodeWarrior compiler). See attached patch to boost 1.30.0 below.
- Petr Ovchenkov
diff -c -r -x CVS boost_1_30_0/libs/filesystem/src/exception.cpp boost/libs/filesystem/src/exception.cpp
*** boost_1_30_0/libs/filesystem/src
John Maddock wrote:
> Subject says it all, as it stands boost/any.hpp isn't even open
> source, please reuse an existing boost licence if possible, thanks,
The license is at the end.
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinf
> I would not mind to change my copyrights to use different wording ---
either
> the one from function library or the "standard" one. The only problem is
> that
>
>boost/graph/transitive_closure.hpp
>
> is generated from
>
>libs/graph/doc/transitive_closure.w
>
> and only Jeremy knows how.
> Done.
Thanks!
John.
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Larry Evans wrote:
[snip]
The code mentioned MAY be very similar to that of J. Kanze available
at:
The articles at:
http://www.gabi-soft.fr/articles-en.html
pretty much confirms that Kanze's code does more (and possibly does it
better) than my code at files/col_io/test_ostreambuf_decorator.zi
Discussion about sequences of pointers is quite interesting,
perhaps sequences of pointees would be more general problem
(remember boost::optional lib.) actually, to have something that
allows to operate intuitivelly on sequences of pointees is a very nice idea.
Regards,
Justinas V.D.
Hi,
While reading The Boost C++ Metaprogramming Library
(http://www.boost.org/libs/mpl/doc/paper/mpl_paper.html),
at section 2.2.1
template< typename T1, typename T2 >
struct derive
{
struct type : N1, N2 {};
};
should be:
template< typename T1, typename T2 >
struct derive
{
struct
In article <[EMAIL PROTECTED]>,
Misha Bergal <[EMAIL PROTECTED]> wrote:
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>> In article <[EMAIL PROTECTED]>,
>> Beman Dawes <[EMAIL PROTECTED]> wrote:
>> >I've been working with Greg Comeau for the last couple of
>> >weeks trying to
>> >resolve
"jvd" <[EMAIL PROTECTED]> writes:
> Discussion about sequences of pointers is quite interesting,
> perhaps sequences of pointees would be more general problem
> (remember boost::optional lib.) actually, to have something that
> allows to operate intuitivelly on sequences of pointees is a very nice
At 03:28 AM 6/16/2003, Misha Bergal wrote:
>
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>> Sent: Saturday, June 14, 2003 4:32 PM
>...
>> In article <[EMAIL PROTECTED]>,
>> Beman Dawes <[EMAIL PROTECTED]> wrote:
>> >I've been working with Greg Comeau for the
No one replied to this, which I'm interpreting as an "OK".
Thus I've committed the changes to tools/regression/process_jam_log.cpp and
compiler_status.cpp to implement the change.
Also, I'd say John should go ahead and make the corresponding change to
is_union_test.
--Beman
At 05:49 PM 6/13/2
Is this of any interest for boost? Some library implementations (for
instance STLport) return a value of container::max_size that doesn't
depend on the corresponding allocator. For instance, for vector
STLport returns:
size_type(-1) / sizeof(T)
As a result, if one uses his own allocator which
I understand that this is not normal, but in this case there
is a lot of work to do to create the files and I am reluctant to
do this if the result is not ultimately going to be accepted.
So I'd prefer agreement in principle first to the way of presenting the
constants,
and to the actual constants
While writing some other code, I checked out how some of the macros in
Boost.Test are implemented. The BOOST_CHECK_THROW and
BOOST_CHECK_EXCEPTION macros flag when an intentional exception was
missed and when the expected exception type was caught. But what about
when an exception of the _wro
In the Boost sandbox CVS, I started a memory library with auto_array,
an array-based variant of std::auto_ptr. It's in the following files
ROOT/boost/memory_fwd.hpp
ROOT/boost/memory/auto_array.hpp
ROOT/boost/libs/memory/doc/auto_array.html
ROOT/boost/libs/memory/
"Daryle Walker" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> While writing some other code, I checked out how some of the macros in
> Boost.Test are implemented. The BOOST_CHECK_THROW and
> BOOST_CHECK_EXCEPTION macros flag when an intentional exception was
> missed and when the
Hi,
I was wondering if it was possible to have two weak pointers that together
own an object. That is, if one of the two is destroyed the other fails to
construct a shared_ptr, but as long as both exist the object is not
destroyed, even if no other weak/shared ptr exists. This would come handy
On Sunday, June 15, 2003, at 10:15 AM, Robert Ramey wrote:
H - I never imagined that something like this would be so
problematic.
For now with my VC 7.0 compiler I can use the following and it gives
me almost exactly what I need. The warning message points exactly to
the place in my code
Bugs item #755724, was opened at 2003-06-17 10:19
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=107586&aid=755724&group_id=7586
Category: static_assert
Group: None
Status: Open
Resolution
John Maddok wrote:
>Another problem (I think) is that with BOOST_STATIC_ASSERT you know compilation will
>stop.
>However, a BOOST_STATIC_WARNING would keep re-apearing in each translation unit
>#including your file:
>// boost_file.hpp
>BOOST_STATIC_WARNING( "we're in boost_file.hpp")
>// fil
On Monday, June 16, 2003, at 9:09 AM, Vladimir Prus wrote:
Daryle Walker wrote:
In CVS, I added an example file to the CRC library. I changed the
documentation to point to the example file.
Daryle,
I see this code in the example:
do
{
ifs.read( buffer
24 matches
Mail list logo
