>From: "David Abrahams" <[EMAIL PROTECTED]>
> Terje Slettebø <[EMAIL PROTECTED]> writes:
>
> >> C:\Program Files\Boost\boost_1_30_0\boost/lexical_cast.hpp(74) :
warning
> > C4512: 'no_lexical_conversion > std::char_traits,class std::allocator >,long>' : assignment
> > operator could not be generat
Thanks! I noticed that this change leads to different behavior when
assigning rules. Consider this code:
typename rule_::type Identifier;
typename rule_::type Function;
typename rule_::type Predicate;
typename rule_::type Variable;
Identifier = lexeme_d[token_node_d[(alpha_p | '_' | '
> Yes, I'd like to see that discussion restarted. The Boost
> Install list
> would be the place to hold it.
While we on topic: why don't we have references to these "minor" lists
anywere. I could not find it not on main site, nor on lists.boost.org (which
I presume should mention all lists relat
At 01:58 PM 3/21/2003, William E. Kempf wrote:
>Until we have a more formal installation solution, I think the SRPM's
spec
>file should reside in CVS. It would also be nice to have other
>installation options as well, such as Debian packages (sorrry, not
totally
>familiar with the terminology t
Terje Slettebø <[EMAIL PROTECTED]> writes:
>> C:\Program Files\Boost\boost_1_30_0\boost/lexical_cast.hpp(74) : warning
> C4512: 'no_lexical_conversion std::char_traits,class std::allocator >,long>' : assignment
> operator could not be generated
>
> This is due to that it stores a const std::string
Joaquín Mª López Muñoz wrote:
> 1. Syntax and semantics
> Since bimap follows as closely as possible the interface of std::map,
> there's little IMHO to add or remove from here. The added constraint
> of bidirectionality imposes some behavior that diverges from regular
> maps, though. I don't thi
Daniel Frey wrote:
Sounds reasonable. Which makes me wonder if we shouldn't change the
^
Should be should, shouldn't be shouldn't ;)
Regards, Daniel
--
Daniel Frey
aixigo AG - financial training, research and technology
Schloß-Rahe-Straße 1
David Abrahams wrote:
I can do that. Should we start a new branch for things that would go
into a hypothetical 1.30.1? My feeling is that we should just keep
using the RC_1_30_0 branch, since it's already been tagged where the
release was made.
Sounds reasonable. Which makes me wonder if we shou
"vc" <[EMAIL PROTECTED]> writes:
> My questions/problems are:
>
> 1) Are ok the above steps that I have done? Is it ok that I created it as a
> static lib (this is how I would
> like to have it)?
>
> 2) Are there any preprocessor flags that I have to add to the project? If
> yes from where can I
>
Matthias Troyer <[EMAIL PROTECTED]> writes:
> Dear Boosters,
>
> Unfortunately we could not test 1.30 extensively and thus found a
> problem with the current Boost sources just after a release.
>
> When trying to compile the filesystem library with KAI C++ we
> encounter a problem in
> boost/type_
Matthias Troyer <[EMAIL PROTECTED]> writes:
> Dear Boosters,
>
> Unfortunately we could not test 1.30 extensively and thus found a
> problem with the current Boost sources just after a release.
>
> When trying to compile the filesystem library with KAI C++ we
> encounter a problem in
> boost/type_
Hi George
- Original Message -
From: "George A. Heintzelman" <[EMAIL PROTECTED]>
Date: Friday, March 21, 2003 7:38 pm
Subject: Re: [boost] Bidirectional map preliminary submission
[stuff deleted]
> > 2. Pollution of namespace boost.
> > Apart from bimap, the following types and functio
>From: "John Swartzentruber" <[EMAIL PROTECTED]>
> I downloaded 1.30.0 and tried to build my project. I got a few errors
> that seem to be in boost, primarily in lexical_cast. Also,
> weak_ptr.hpp uses bad_weak_ptr without including
> boost/detail/shared_count.hpp anywhere. I can fix that by
> inc
EXCEPT.DOC
Description: MS-Word document
On Friday, Mar 21, 2003, at 11:51 America/Denver, Gennaro Prota wrote:
On Fri, 21 Mar 2003 10:06:45 -0700, Greg Colvin
<[EMAIL PROTECTED]> wrote:
The idea of the why() member was to preserve context when one
exception
gets caught and a different one gets
John Swartzentruber wrote:
> I downloaded 1.30.0 and tried to build my project. I got a few errors
> that seem to be in boost, primarily in lexical_cast. Also,
> weak_ptr.hpp uses bad_weak_ptr without including
> boost/detail/shared_count.hpp anywhere. I can fix that by
> including it in my code.
Beman Dawes said:
> At 01:11 PM 3/21/2003, Neal D. Becker wrote:
>
> >I have built SRPMS for RH8 for boost1.30.0. They required just minor
> modifications to the spec files. Where should I upload them?
>
> Should that be part of the regular Boost distribution, and thus live in
> CVS? If so, wou
vc said:
> Hi all,
>
> I'm using the boost version 1.30 release, on Win2k and the VC7.1
> compiler.
>
> I'm porting a big application from Unix to Windows. Because for all the
> modules within this app I created
> a VC++ workspace I would like to do the same for the thread library from
> boost.
>
On Fri, 21 Mar 2003 10:06:45 -0700, Greg Colvin
<[EMAIL PROTECTED]> wrote:
>The idea of the why() member was to preserve context when one exception
>gets caught and a different one gets thrown, so you could walk back the
>chain of why()'s asking what() and where(). I bring it up just as a
>design
A bidirectional map is something I've wanted a good implementation of
for a while. I have one that has some terrible performance in memory
and speed, but does what I need in its current context. Having a better
one would be great, so I applaud your submission.
> 1. Syntax and semantics
> Since
I downloaded 1.30.0 and tried to build my project. I got a few errors
that seem to be in boost, primarily in lexical_cast. Also,
weak_ptr.hpp uses bad_weak_ptr without including
boost/detail/shared_count.hpp anywhere. I can fix that by
including it in my code.
These are the warnings in lexical_
At 01:11 PM 3/21/2003, Neal D. Becker wrote:
>I have built SRPMS for RH8 for boost1.30.0. They required just minor
>modifications to the spec files. Where should I upload them?
Should that be part of the regular Boost distribution, and thus live in
CVS? If so, would you be willing to maintain i
> -Original Message-
> From: Eric Niebler [mailto:[EMAIL PROTECTED]
>
> > > The way call_traits is currently implemented,
> > > call_traits::value_type is an int&,
> > > not an int.
> >
> > This is the correct behavior. If you are storing an "int &" and want to
> > return it by value, you
I have built SRPMS for RH8 for boost1.30.0. They required just minor
modifications to the spec files. Where should I upload them?
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Hi All,
I posted this question on boost.users list but did not get
any response.
My first attempt to switch my project from boost 1.29 to
1.30 failed miserably due to compilation errors in random library.
Simple
#include
#include
int main() {return 0;}
Fails with lots o
> > The way call_traits is currently implemented,
> > call_traits::value_type is an int&,
> > not an int.
>
> This is the correct behavior. If you are storing an "int &" and want to
> return it by value, you will return an "int &".
This is some new usage of the term "by value" with which I'm not
I read on the date_time change history about a new function for
calculating ISO 8601 week number.
I should note that this week number is rather useless without
the corresponding year number. ISO 8601 week-based year is not
always the same as the actual year. For example, 2nd January 1999
is week 53
The idea of the why() member was to preserve context when one exception
gets caught and a different one gets thrown, so you could walk back the
chain of why()'s asking what() and where(). I bring it up just as a
design that might be worth resurrecting if it meets your needs.
On Friday, Mar 21, 200
Hi all,
I'm using the boost version 1.30 release, on Win2k and the VC7.1 compiler.
I'm porting a big application from Unix to Windows. Because for all the
modules within this app I created
a VC++ workspace I would like to do the same for the thread library from
boost.
For this I did the followin
Dear Boosters,
Unfortunately we could not test 1.30 extensively and thus found a
problem with the current Boost sources just after a release.
When trying to compile the filesystem library with KAI C++ we encounter
a problem in
boost/type_traits/is_base_and_derived.hpp
It seems that the workaro
Greg Colvin wrote:
> std::exception used to have a why() member that returned the list of
> exceptions leading to the one caught. Is that part of what you want?
Not exactly. I'm not too bothered about the history of the exceptions,
I'm simply concerned with formatting useful error messages for
std::exception used to have a why() member that returned the list of
exceptions leading to the one caught. Is that part of what you want?
On Friday, Mar 21, 2003, at 03:58 America/Denver, Alisdair Meredith
wrote:
Darren Cook wrote:
I wanted something like the call stack that shows in python or
Dave Gomboc wrote:
> Section "Portability"
>
>> 8. Intel 7.0VisualAge C++ 5.02
>
> should be split into two lines.
Thanks for the various doc-bug reports. Duly noted.
--
Joel de Guzman
joel at boost-consulting.com
http://www.boost-consulting.com
http://spirit.sf.net
__
Is anyone working on RPMS for 1.30.0?
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
First of all, congratulations to all for the new 1.30.0 baby.
I've boostified my bimap library so that it can be more easily
reviewed. Now bimap lives into namespace boost and some
metastuff have been removed in favor of utilities already
provided by Boost itself.
The bimap.hpp header has been upl
[EMAIL PROTECTED] writes:
>> From: Eric Niebler [mailto:[EMAIL PROTECTED]
>> Is this an oversight in call_traits?
>
> Look at the "Examples" table in the call_traits documentation. If this is
> not the behavior you want, use call_traits (or, generically,
> call_traits::type>).
>
>> Or just an u
Russell Hind wrote:
> I had the same problem with C++Builder 6 when first using the filesystem
> library. The default builds for filesystem are single threaded. If
> your application is multi-threaded, then you need to re-build the
> filesystem library with multi-threading (it uses mutexes somew
> -Original Message-
> From: Eric Niebler [mailto:[EMAIL PROTECTED]
>
> The way call_traits is currently implemented,
call_traits::value_type
> is an int&, not an int.
This is the correct behavior. If you are storing an "int &" and want to
return it by value, you will return an "int &".
Tony Cheung wrote:
I am trying to use the date-time library of boost. However, I come into a
lot of linking problems.
I experienced similar things too when attempting to use it.
Did I do anything wrong? Thank you.
In order to get it to work I included a file that contained the following:
#inclu
"Jeff Garland" <[EMAIL PROTECTED]> writes:
>> While we're on the subject of broken links, the link to date_time change
>> history doesn't work from the boost home page
>> http://www.boost.org/libs/date_time/doc/Changes.html
>
> Really sorry about this. I have checked it in and attached it for
>
> gcc testgregorian_calendar.cpp -I/home/tony/work/boost_1_29_0/ -lstdc++
>
> It gives many linking problems, such as,
>
> /tmp/ccMBFqqI.o: In function `main':
> /tmp/ccMBFqqI.o(.text+0x154): undefined reference to
> `boost::date_time::gregorian_calendar_base
> long, unsigned short, unsigned s
Hello
I have now added the following custom cast operator into my copy of
shared_ptr class:
#ifdef DARK_FORCE
operator shared_ptr&()
{
return reinterpret_cast &>(*this);
}
#endif // DARK_FORCE
and hence the following code compiles easily:
> While we're on the subject of broken links, the link to date_time change
> history doesn't work from the boost home page
> http://www.boost.org/libs/date_time/doc/Changes.html
Really sorry about this. I have checked it in and attached it for
those that want to patch 1.30. Just add the attach
Rene Rivera wrote:
I'm very interested in having tree container concepts in Boost. It's my
plan
to submit such a thing to Boost in the summer. Currently I only have a
rank_tree implementation (log2 n, or better on all ops) so having someone
else work on other types of tree implementations would b
Darren Cook wrote:
> I wanted something like the call stack that shows in python or java when an
> uncaught exception occurs; if you're also suggesting a snapshot of local
> vars/parameters then I'll be in heaven and may never need to fire up a
> debugger again :-).
This is exactly NOT what I am
Hi,
I am trying to use the date-time library of boost. However, I come into
a lot of linking problems.
In boost_1_29_0/libs/date_time/test,
gcc testgregorian_calendar.cpp -I/home/tony/work/boost_1_29_0/ -lstdc++
It gives many linking problems, such as,
/tmp/ccMBFqqI.o: In function `main':
/tm
45 matches
Mail list logo
