This is on version 2.2 that is dated on 5 July 2003. I haven't read
any messages since July 12th, so I haven't seen any other reviews yet.
I think this library should be accepted. I have some suggestions for
fixes and other changes.
1. We have two math-related namespaces already. The boost::
> Douglas Paul Gregor <[EMAIL PROTECTED]> writes:
>
> >> Doesn't look like there has been any activity on signals and
multi_array.
> >> Are the developers aware of the need for action?
> >
> > I'll try to work on Signals tonight.
>
> Hint: turn the body of your policies class into the body of your
Matthias Troyer <[EMAIL PROTECTED]> writes:
>> Who's going to fix up the graph library?
>
> A quick fix to get my codes to compile again (but which does not solve
> the problem) is to just remove the BOOST_STATIC_ASSERT in line 276 of
> iterator_adaptor.hpp.
Yes, we know about that.
I'm still wa
"Marshall Clow" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> "Joe Gottman" <[EMAIL PROTECTED]> wrote:
> >Suppose I have a vector and I want to use indirect_iterator to
create
> >an iterator that allows the user to read but not modify the objects
pointed
> >to by elements of the ve
Marshall Clow <[EMAIL PROTECTED]> writes:
>> I'm sure this is possible, but the documentation doesn't really say how to
>>do it.
>
> is there some reason you can't use const_iterator?
Yeah, it wouldn't work.
There's an example of how to do this in
libs/utility/indirect_iterator_example.cpp
HT
Daniel Frey <[EMAIL PROTECTED]> writes:
> On Tue, 15 Jul 2003 16:26:43 +0200, David Abrahams wrote:
>
>> What does everybody think about doing a 1.30.1 release "RSN?"
>
> I think it's too late, let's go for a 1.31.0. I think that we'll hear
> about problems with the 1.31.0 really soon after releas
Beman Dawes <[EMAIL PROTECTED]> writes:
> At 11:50 AM 7/15/2003, David Abrahams wrote:
> >Beman Dawes <[EMAIL PROTECTED]> writes:
> >
> >> At 10:26 AM 7/15/2003, David Abrahams wrote:
> >>
> >> >Dominique Devriese <[EMAIL PROTECTED]>
> writes:
> >> >
> >> >>> In general, they are r
"Joe Gottman" <[EMAIL PROTECTED]> wrote:
Suppose I have a vector and I want to use indirect_iterator to create
an iterator that allows the user to read but not modify the objects pointed
to by elements of the vector. In other words, I want to do the following:
typedef /*whatever */ my_iterator;
I have posted the first "boostified" version of FC++ to the YahooGroups
files section; it is called "fcpp".
http://groups.yahoo.com/group/boost/files/
--
Background
--
FC++ is a library for functional programming. In FC++ we program with
"functoids" (classes which define operat
On Tuesday, July 15, 2003, at 07:31 AM, David Abrahams wrote:
Matthias Troyer <[EMAIL PROTECTED]> writes:
Sorry, Here is an example that shows the problem in a simple case:
#include
#include
int main()
{
boost::adjacency_list
boost::no_property, boost::no_property, boost::no_property,
Suppose I have a vector and I want to use indirect_iterator to create
an iterator that allows the user to read but not modify the objects pointed
to by elements of the vector. In other words, I want to do the following:
typedef /*whatever */ my_iterator;
my_iterator it(theVector.begin());
co
- Original Message -
From: "Daniel Frey" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, July 15, 2003 11:38 PM
Subject: [boost] Re: plans for a bugfix release ?
> On Tue, 15 Jul 2003 16:26:43 +0200, David Abrahams wrote:
>
> > What does everybody think
On Tue, 15 Jul 2003 23:20:06 +0200, Peter Dimov wrote:
> Daniel Frey wrote:
>> On Tue, 15 Jul 2003 22:22:03 +0200, Peter Dimov wrote:
>>
+#include
+#if defined(BOOST_INTEL)
+#include
+#endif
>>>
>>> Dependencies. I hate dependencies.
>>
>> Do you have a better idea?
>
> Seve
Hello..
Typically what i do for releases is something along the line of this.
prject - x,yy,zz
x - major architecture changes.
yy - minor changes. (uneven for development).
zz - no interface changes. bug fixes.
I try to release the zz often (for stable). Everytime there is a critical
fix or a fe
On Tue, 15 Jul 2003 16:26:43 +0200, David Abrahams wrote:
> What does everybody think about doing a 1.30.1 release "RSN?"
I think it's too late, let's go for a 1.31.0. I think that we'll hear
about problems with the 1.31.0 really soon after release and probably a
1.31.1 can follow shortly after.
Bill,
Bill Seymour <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I've upload fixdec23.zip to the Yahoo files section.
>
> I made some changes that Jens suggested to allow compiling with
> Comeau and gcc; and I've made the is_bounded and is_modulo fixes
> that Fernando suggested alo
Daniel Frey wrote:
> On Tue, 15 Jul 2003 22:22:03 +0200, Peter Dimov wrote:
>
>>> +#include
>>> +#if defined(BOOST_INTEL)
>>> +#include
>>> +#endif
>>
>> Dependencies. I hate dependencies.
>
> Do you have a better idea?
Several, like (1) using __INTEL_COMPILER for detection and (2) isolating the
On Tue, 15 Jul 2003 22:29:50 +0200, David Abrahams wrote:
> Daniel Frey <[EMAIL PROTECTED]> writes:
>
>> To explain the bug a bit: When you create a small test case, you'll
>> probably get the error from the compiler you are looking for. If you
>> put the checked_delete in it's own header, it sti
On Tue, 15 Jul 2003 22:22:03 +0200, Peter Dimov wrote:
> Daniel Frey wrote:
>>
>> To explain the bug a bit: When you create a small test case, you'll
>> probably get the error from the compiler you are looking for. If you
>> put
>> the checked_delete in it's own header, it still works as long as y
At 11:50 AM 7/15/2003, David Abrahams wrote:
>Beman Dawes <[EMAIL PROTECTED]> writes:
>
>> At 10:26 AM 7/15/2003, David Abrahams wrote:
>>
>> >Dominique Devriese <[EMAIL PROTECTED]>
writes:
>> >
>> >>> In general, they are released when all of Boost is ready. I think
>> >>> it would be a *rea
On Tue, 15 Jul 2003 19:19:08 +0200, Thomas Witt wrote
> David Abrahams wrote:
> > Beman Dawes <[EMAIL PROTECTED]> writes:
> >
> > When we released 1.30.0, despite extensive pre-release testing, it
> > went out with several prominent showstopper bugs. Don't you think
> > we'll make the same mista
Daniel Frey <[EMAIL PROTECTED]> writes:
> To explain the bug a bit: When you create a small test case, you'll
> probably get the error from the compiler you are looking for. If you put
> the checked_delete in it's own header, it still works as long as you
> include the header with
You probably
Daniel Frey wrote:
>
> To explain the bug a bit: When you create a small test case, you'll
> probably get the error from the compiler you are looking for. If you
> put
> the checked_delete in it's own header, it still works as long as you
> include the header with
>
> #include "my_header.h"
>
> but
I've upload fixdec23.zip to the Yahoo files section.
I made some changes that Jens suggested to allow compiling with
Comeau and gcc; and I've made the is_bounded and is_modulo fixes
that Fernando suggested along with interoperatability with
unsigned as well as int.
Fernando,
I think that max_sca
On Tue, 15 Jul 2003 10:58:10 +0200, Daniel Frey wrote:
> Also, it seems possible to create a work-around for boost. I'll post a
> patch for discussion soon :)
Here's the patch, applying the work-around for all versions of the Intel
compiler. Of course we should restrict this once we find out whic
> David Abrahams wrote:
> > Beman Dawes <[EMAIL PROTECTED]> writes:
> >
> > When we released 1.30.0, despite extensive pre-release testing, it
> > went out with several prominent showstopper bugs. Don't you think
> > we'll make the same mistake for 1.31.0? Also, AFAICT 1.30.1 can go
> > out
"Jonathan David Turkanis" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> > You have read/write member functions of your source/sink/filter
concepts
> > virtual. If one went for efficiency she would stay away from virtual
> > functions. With such a design you leave a user no choic
Hi Bill,
Yes, 'precision' is what I meant.
I used the term' digits' because that's what is used for 'numeric_limits<>',
but I much prefer 'precision'.
There is one thing I noticed though that I'd like you to confirm:
Because of the implementation (a normalized rep with two separate int_type
member
Ronald Garcia <[EMAIL PROTECTED]> writes:
> David Abrahams wrote:
>> I don't understand it, but Ron Garcia seems to have a fondness for
>> checking duplicates of information that is hosted elsewhere into his
>> library's tree.
>
> Since you and I previously discussed why multi_array has a private
David Abrahams wrote:
Beman Dawes <[EMAIL PROTECTED]> writes:
When we released 1.30.0, despite extensive pre-release testing, it
went out with several prominent showstopper bugs. Don't you think
we'll make the same mistake for 1.31.0? Also, AFAICT 1.30.1 can go
out much, much sooner.
I agree w
David Abrahams wrote:
> I don't understand it, but Ron Garcia seems to have a fondness for
> checking duplicates of information that is hosted elsewhere into his
> library's tree.
Since you and I previously discussed why multi_array has a private
copy of iterator_adaptors, I'm assuming a ":-)" g
Fernando Cacciola wrote:
>
> OK.
> So, correct me if I'm wrong:
> For any given decimal with some int_type, a 'digits' constant is
> associated with it which comes from numeric_limits::digits10.
> This constant identifies the maxium number of digits (in both the
> whole and fractional parts) that a
Beman Dawes <[EMAIL PROTECTED]> writes:
> At 10:26 AM 7/15/2003, David Abrahams wrote:
>
> >Dominique Devriese <[EMAIL PROTECTED]> writes:
> >
> >>> In general, they are released when all of Boost is ready. I think
> >>> it would be a *really* good idea for Boost to do at least one minor
> >
At 10:26 AM 7/15/2003, David Abrahams wrote:
>Dominique Devriese <[EMAIL PROTECTED]> writes:
>
>>> In general, they are released when all of Boost is ready. I think
>>> it would be a *really* good idea for Boost to do at least one minor
>>> version release shortly after any major version release.
Below is the SourceForge reply to my support request to SourceForge titled
"CVS performance (via SSH) sinking".
If any Boost developers still run into "`FATAL ERROR: Network error:
Connection timed out' from cvs server" or similar problems, you might want
to re-open support request #771637, and
Hi Bill,
Bill Seymour <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Fernando,
>
> Thanks for your input.
>
> The "scale" really is intended to be the number of decimal digits
> to the right of the decimal point; so, yes, if int_type on your
> system is 64 bits, and if you specify a
Jaakko Jarvi wrote code that looks like this:
template
struct disable_if: public enable_if< !B, T> {};
I have a question regarding compile time:
Do you have experience about whether this elegant solution
might have some compile time penalty due to inheritance?
Or is this faster than doublin
Dominique Devriese <[EMAIL PROTECTED]> writes:
>> In general, they are released when all of Boost is ready. I think
>> it would be a *really* good idea for Boost to do at least one minor
>> version release shortly after any major version release. Now that
>> we have a reasonable testing strategy
Dominique Devriese <[EMAIL PROTECTED]> writes:
> David Abrahams writes:
>
>>> Hi,
>>>
>>> I'm the main developer of Kig [1]. I have just committed the code
>>> for python scripting to the CVS repository
>
>> Using Boost.Python? Cool!
>
> Yups, I was going to post something separately about inclu
Fernando,
Thanks for your input.
The "scale" really is intended to be the number of decimal digits
to the right of the decimal point; so, yes, if int_type on your
system is 64 bits, and if you specify a scale of 18, then no
/whole/ decimal digits will be allowed to the left of the point.
(You mig
I remember that there are 2 types of separators in boost tokenizer:
returnable and ignorable. Set "-" as returnable separator, and "," as
ignorable. It should give you all the information you need.
Gennadiy.
"lattice" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> If we print some
I've seen from the regression tests that the Intel compiler (7.1) seems
to have a problem with checked_delete. I looked into it and found out
what triggers the bug. Has anyone else done something similar and
reported the bug to Intel or should I do it?
Also, it seems possible to create a work-a
You need to pass a separator into the tokenizer that only separates on
',' (i'm not sure if this code compiles, but you get the idea
std::string Pages("2,3,5-7");
char_separator CommaSep(",");
tokenizer > Tokenizer(Pages,CommaSep);
This will split it up into
2
3
5-7
You will then nee
If we print some pages ,we can select pages in a range to print.
for example,if we enter 2,3,5-7 in Ms-word print dialog,then page
2,3,5,6,7 is printed.
Now questions is :
if we get a string like this "2,3,5-7",if we use boost::tokenizer,
we can only get 2,3,5,7. eventually some information is lost
44 matches
Mail list logo
