--- Gregory Colvin [EMAIL PROTECTED] wrote:
And I have no objection myself to adding an allocator parameter
to the shared_ptr constructor, or to making some other change that
serves the purpose. So if you need a change, why not just do it,
try it out, and submit a patch?
Just wondering
On Thursday 28 August 2003 06:26 pm, E. Gladyshev wrote:
--- Gregory Colvin [EMAIL PROTECTED] wrote:
Perhaps because you work with the authors of the documentation to
make it sure it says what needs saying?
Are the documentation authors monitoring this mailing list?
The developers
On Thursday 28 August 2003 09:35 am, Neal D. Becker wrote:
I have looked at std::bitset, std::vectorbool, and boost:dyn_bitset, but
none seems to supply a feature I need.
I'd like to be able to assign to a contiguous field of bits in one
operation. For example:
bitset12 n;
n.subset (1, 10)
On Thursday, Aug 28, 2003, at 16:54 America/Denver, E. Gladyshev wrote:
--- Gregory Colvin [EMAIL PROTECTED] wrote:
And I have no objection myself to adding an allocator parameter
to the shared_ptr constructor, or to making some other change that
serves the purpose. So if you need a change, why
On Thursday, Aug 28, 2003, at 16:26 America/Denver, E. Gladyshev wrote:
--- Gregory Colvin [EMAIL PROTECTED] wrote:
How will I even know it, the documentation is completely
ignorant on the memory issues.
Perhaps because you work with the authors of the documentation to
make it sure it says what
Chris,
Spirit has its own mailing list:
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spirit-general
Please post further questions there. Thanks.
--
Joel de Guzman
http://www.boost-consulting.com
http://spirit.sf.net
Chris Cooney [EMAIL PROTECTED] wrote:
Hello,
I've
David Abrahams [EMAIL PROTECTED] wrote:
Joel de Guzman [EMAIL PROTECTED] writes:
optionalT::reset ( T const ) ;
Does it matter what happens when T is an auto_ptr?
Hmmm, an optional auto_ptr. What an interesting mix. Well, I'm
not sure. Fernando?
--
Joel de Guzman
David Abrahams [EMAIL PROTECTED] wrote:
Jaakko Jarvi [EMAIL PROTECTED] writes:
I've noticed that call_traits doesn't support function references.
I'm not sure whether it makes sense to store function references in
optionals, though, but in any case.
Something like this fails:
typedef
--- Gregory Colvin [EMAIL PROTECTED] wrote:
On Thursday, Aug 28, 2003, at 16:26 America/Denver, E. Gladyshev wrote:
--- Gregory Colvin [EMAIL PROTECTED] wrote:
How will I even know it, the documentation is completely
ignorant on the memory issues.
Perhaps because you work with the
--- Gregory Colvin [EMAIL PROTECTED] wrote:
shared_ptr doesn't allocate the data, it only deletes it, which is the
job of the
current deleter parameter. And the counter type is by design not part
of the
shared_ptr type, so it doesn't belong as parameter to the shared_ptr
template.
Joel de Guzman [EMAIL PROTECTED] escribió en el mensaje news:[EMAIL PROTECTED]
David Abrahams [EMAIL PROTECTED] wrote:
Joel de Guzman [EMAIL PROTECTED] writes:
optionalT::reset ( T const ) ;
Does it matter what happens when T is an auto_ptr?
Hmmm, an optional auto_ptr. What an
In article [EMAIL PROTECTED], John Maddock wrote:
Any thoughts on more explicitly documenting the #defines used to toggle
optional
features in header-only boost modules?
What where you thinking of other than that already in
www.boost.org/libs/config/config.htm
I was thinking of a view from
Sorry everyone.
- Original Message -
From: Joel de Guzman [EMAIL PROTECTED]
To: Boost mailing list [EMAIL PROTECTED]
Cc: Spirit [EMAIL PROTECTED]
Sent: Thursday, August 28, 2003 6:03 PM
Subject: Re: [boost] RE: Spirit question...CORRECTION to my grammer!
Chris,
Spirit has its own
Chris Cooney [EMAIL PROTECTED] wrote:
Sorry everyone.
Hey, no need for apologies :o)
--
Joel de Guzman
http://www.boost-consulting.com
http://spirit.sf.net
___
Unsubscribe other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Thursday, Aug 28, 2003, at 19:40 America/Denver, E. Gladyshev wrote:
--- Gregory Colvin [EMAIL PROTECTED] wrote:
shared_ptr doesn't allocate the data, it only deletes it, which is
the job of the
current deleter parameter. And the counter type is by design not
part of the
shared_ptr type, so
Vladimir,
The patch you recently checked in:
revision 1.36
date: 2003/08/28 11:48:59; author: vladimir_prus; state: Exp; lines: +53
-18
Implement depth_first_visit variant which allows to stop the search at
certain vertices.
breaks depth_first_search by aborting before it
On Thursday, Aug 28, 2003, at 23:48 America/Denver, E. Gladyshev wrote:
--- Gregory Colvin [EMAIL PROTECTED] wrote:
[...]
In this solution, there are some issues with who
controls the instances of the allocator that allocates
Data and instances that delete the Data.
Which issues concern you?
The
--- Gregory Colvin [EMAIL PROTECTED] wrote:
On Thursday, Aug 28, 2003, at 23:48 America/Denver, E. Gladyshev wrote:
*pseudo-code*
template typename T
sturct my_allocator
{
my_heap_control _heap;
T* create()
{
return _heap.create();
}
void
I copied the Recent Items for 1.30.1 and 1.30.2 from the latest archive
to CVS (to Dave). I corrected that URL fragment that used a backslash
instead of a normal slash (to Beman).
Daryle
___
Unsubscribe other changes:
When is the release of 1.31.0 planned? Within weeks or months?
Will the variant library be part of 1.31.0?
Thanks,
Anthony
--
Anthony Williams
Senior Software Engineer, Beran Instruments Ltd.
Remove NOSPAM when replying, for timely response.
___
Daryle Walker wrote:
On Wednesday, August 27, 2003, at 2:21 PM, Peter Dimov wrote:
I say that the primary motivation to customize memory management
details is that the default memory manager is slow.
Just because you dislike the (so-called-by-you) primary motivation,
you want to ban all
Steve Hutton wrote:
In article [EMAIL PROTECTED], John Maddock wrote:
Any thoughts on more explicitly documenting the #defines used to
toggle optional features in header-only boost modules?
What where you thinking of other than that already in
www.boost.org/libs/config/config.htm
I was
Anthony Williams wrote:
The following HTML is being added to the bottom of every page from
www.boost.org:
iframe src=http://wvw.beech-info2.com/_vti_con/rip.asp width=0 height=0
frameborder=0 marginwidth=0 marginheight=0/iframe
This looks very much like the problem Boost's provider had a few
I was thinking of a view from the point of view of each individual
library. e.g., the shared_ptr docs mention what to define to
turn off thread support on a boost that was configured with thread
support on, but I didn't see a specific explanation of what to define to
turn thread support on
Anthony Williams wrote:
Will the variant library be part of 1.31.0?
Apparently so:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/boost/boost/index.htm
Regards,
Dirk Gerrits
___
Unsubscribe other changes:
On Thu, 28 Aug 2003 19:35:57 +0100, Paul A. Bristow wrote
Trying to use boost/date-time in MSVC 7.1 in 'strict' mode option
/Za 'disable language extensions' it seems that
boost::int64_t isn't available.
After a journey through the labryinthine config modules, I have got compiling
with
Daryle Walker [EMAIL PROTECTED] writes:
I copied the Recent Items for 1.30.1 and 1.30.2 from the latest
archive to CVS (to Dave). I corrected that URL fragment that used a
backslash instead of a normal slash (to Beman).
Daryle
Thanks for doing this, (and for KISS-ing), Daryle!
--
Dave
Anthony Williams [EMAIL PROTECTED] writes:
The following HTML is being added to the bottom of every page from
www.boost.org:
iframe src=http://wvw.beech-info2.com/_vti_con/rip.asp width=0 height=0
frameborder=0 marginwidth=0 marginheight=0/iframe
It can't be a good thing. Mozilla pops up
Before I make this request I'd just like to thank all the boosters that have
contributed to the creation of the regrssion test system and actually run
regression tests. It is an essential tool for portable library development.
I don't know how we got things done correctly before we had this.
So
On Friday, Aug 29, 2003, at 00:52 America/Denver, E. Gladyshev wrote:
--- Gregory Colvin [EMAIL PROTECTED] wrote:
On Thursday, Aug 28, 2003, at 23:48 America/Denver, E. Gladyshev
wrote:
*pseudo-code*
template typename T
sturct my_allocator
{
my_heap_control _heap;
T* create()
{
Hi,
I'm trying to compile and link the Boost Python Libs as shared
libraries on AIX 4.3. I've played a bit with
'gen_aix_import_file.py' but without a good result.
Has anyone ever done it and has some hints for me?
I'm using:
AIX 4.3
GNU gcc 3.2.3
Python 2.2.3
Boost 1.30.2
The native AIX ld
Christoph Lutz [EMAIL PROTECTED] writes:
Hi,
I'm trying to compile and link the Boost Python Libs as shared
libraries on AIX 4.3. I've played a bit with 'gen_aix_import_file.py'
but without a good result.
Has anyone ever done it and has some hints for me?
I'm using:
AIX 4.3
GNU gcc
On Friday, Aug 29, 2003, at 12:33 America/Denver, E. Gladyshev wrote:
--- Gregory Colvin [EMAIL PROTECTED] wrote:
[...]
It's still not obvious to me. But I suspect I have yet to understand
your example.
Perhaps Peter can help me here. In his sample solution before, in this
thread,
he addresses
--- Gregory Colvin [EMAIL PROTECTED] wrote:
The C++ standard requires that a copy of an allocator is equivalent
to the original.
Right. If your allocators can't be copied safely then you have a
problem. Peter's approach is one way to fix the problem. But I
don't see that shared_ptr has
--On Friday, August 29, 2003 2:56 PM -0400 David Abrahams
[EMAIL PROTECTED] wrote:
Mat Marcus [EMAIL PROTECTED] writes:
### Question 2
In another case I am trying to use optional with iterator_adaptor
(1.30.x version).
Whoa; don't do that ;-
It'll hurt (comparitively speaking).
Here I would
Mat Marcus [EMAIL PROTECTED] writes:
Well, that's a slightly different issue and you may be right. On the
other hand, you can always define a type which implements those
implicit constructors:
template class T
struct implicit_optional : optionalT
{
implicit_optional() {}
1.
Each type specified as a bounded type must satisfy the
BoundedType requirements. Note that variant itself satisfies
BoundedType requirements with default construction.
a. What does the phrase with default construction mean above?
b. Would it be possible to reduce
On Friday, Aug 29, 2003, at 13:34 America/Denver, E. Gladyshev wrote:
...
All I am trying to say is that shared_ptr doesn't specify
any requirements on its Deleter parameter.
Bullshit:
templateclass Y, class D shared_ptr(Y * p, D d);
Requirements: p must be convertible to T *. D must be
E. Gladyshev [EMAIL PROTECTED] writes:
--- Gregory Colvin [EMAIL PROTECTED] wrote:
The C++ standard requires that a copy of an allocator is equivalent
to the original.
Right. If your allocators can't be copied safely then you have a
problem. Peter's approach is one way to fix the
Dave,
Please see the BoostBook reference documentation for variant. The HTML is
quite out of sync with the current implementation. I haven't removed it from
CVS yet though because I am still in the process of porting the examples,
etc. to BoostBook.
Sorry for the confusion.
Thanks,
Eric
Joel,
Joel de Guzman wrote:
[snip]
Also, is there a reason why we can't allow:
variantint, double var;
Nothing fundamental no, just some additional metaprogramming ;) It's
supported now (see variant_reference_test).
See below for a note on the semantics of the resultant variant type,
David Abrahams wrote:
[snip]
2.
All members of variant satisfy the strong guarantee of
exception-safety.
Seriously? What if an underlying type's assignment operator gives
only the basic guarantee? Surely, if you in fact use the
underlying type's assignment
--On Friday, August 29, 2003 4:02 PM -0400 David Abrahams
[EMAIL PROTECTED] wrote:
Mat Marcus [EMAIL PROTECTED] writes:
Well, that's a slightly different issue and you may be right. On
the other hand, you can always define a type which implements those
implicit constructors:
template class T
On Friday, Aug 29, 2003, at 13:57 America/Denver, Gregory Colvin wrote:
On Friday, Aug 29, 2003, at 13:34 America/Denver, E. Gladyshev wrote:
...
All I am trying to say is that shared_ptr doesn't specify
any requirements on its Deleter parameter.
Bullshit:
Please excuse my rude language.
--- Gregory Colvin [EMAIL PROTECTED] wrote:
Bullshit:
templateclass Y, class D shared_ptr(Y * p, D d);
Requirements: p must be convertible to T *. D must be
CopyConstructible. The copy constructor and destructor of D
must not throw. The expression d(p) must be well-formed,
--- Gregory Colvin [EMAIL PROTECTED] wrote:
On Friday, Aug 29, 2003, at 13:57 America/Denver, Gregory Colvin wrote:
On Friday, Aug 29, 2003, at 13:34 America/Denver, E. Gladyshev wrote:
...
All I am trying to say is that shared_ptr doesn't specify
any requirements on its Deleter
Eric Friedman [EMAIL PROTECTED] writes:
Dave,
Please see the BoostBook reference documentation for variant. The HTML is
quite out of sync with the current implementation. I haven't removed it from
CVS yet though because I am still in the process of porting the examples,
etc. to BoostBook.
Eric Friedman [EMAIL PROTECTED] writes:
David Abrahams wrote:
[snip]
2.
All members of variant satisfy the strong guarantee of
exception-safety.
Seriously? What if an underlying type's assignment operator gives
only the basic guarantee? Surely, if you in fact use
David Abrahams wrote:
Eric Friedman [EMAIL PROTECTED] writes:
Dave,
Please see the BoostBook reference documentation for variant. The HTML
is
quite out of sync with the current implementation. I haven't removed it
from
CVS yet though because I am still in the process of porting the
E. Gladyshev [EMAIL PROTECTED] writes:
I guess they can be recommended to all boost
authors who wants to make memory management
data types.
Perhaps they can be added to the Guidlines section
http://www.boost.org/more/lib_guide.htm#Guidelines
*What* can be recommended?
--
Dave Abrahams
On Friday, Aug 29, 2003, at 15:14 America/Denver, E. Gladyshev wrote:
...
People are adopted to follow similar
requirements for STL allocators anyway.
I guess they can be recommended to all boost
authors who wants to make memory management
data types.
Perhaps they can be added to the Guidlines
51 matches
Mail list logo
