> template
> class nilable {
Was that small enough to be considered not copyrightable, warrantable, etc.
?
If so, fine. Otherwise I guess I have to disclaim any warranty, etc. Boost
Public Licence?
Dave
___
Unsubscribe & other changes: http
> Right now I am questioning whether the
> pointer-like semantics is worth it to me. I would probably prefer that
> clients type more to test whether a value is initialized so that they
> can type less to call a function that takes an optional as a parameter
> when they have a value to pass in. Sor
--- Gregory Colvin <[EMAIL PROTECTED]> wrote:
>
> At the least, we could add the following bullet
>
>* Discussion of memory management strategy.
>
> to http://www.boost.org/more/lib_guide.htm#Documentation
I think it is a great start.
> I'm reluctant to say very much more at this point, a
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" se
"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?
--
Dav
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
"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
"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 Boo
--- 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 Del
--- Gregory Colvin <[EMAIL PROTECTED]> wrote:
> Bullshit:
>
>template 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, must
>
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.
_
--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
str
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 assignm
Joel,
Joel de Guzman wrote:
[snip]
> Also, is there a reason why we can't allow:
>
> variant 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, though.
>
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
_
"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
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:
template shared_ptr(Y * p, D d);
Requirements: p must be convertible to T *. D must be
CopyConstructible.
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 red
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
>> struct implicit_optional : optional
>> {
>>implicit_optional() {}
>>
--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 wo
--- 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_pt
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
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 like the "base" for my iterator_adaptor to be, say,
> boost::optional. Th
I'm finally getting around to playing with optional. A couple of
questions.
### Question 1
One of the projects that I am working on makes heavy use of
tuples/pairs and as a result tie. It appears that some of the code may
be improved by the use of optional. It is not clear to me whether I
can
--- 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 this problem nicely by using static functions
that take reference
Also "swap" is often the fastest way to move an non POD. I spent some
time writing something similar to what you describe...
http://groups.yahoo.com/group/boost/files/move.tar.gz
The idea is that you have four ways to move an object depending on
whether you need to construct the destination or d
Do I understand correctly that with MSVC 7.1 option /Za
#define BOOST_HAS_MS_INT64
merely makes int64_t available as the ONLY language extension?
(I am only trying to uniformly compile MY modules (which all use date-time)
without language extensions and warnings at level 4).
Paul
Paul A Bristo
On Friday, Aug 29, 2003, at 10:48 America/Denver, E. Gladyshev wrote:
--- Gregory Colvin <[EMAIL PROTECTED]> wrote:
[...]
Does it make sense?
Not to me. Sounds like a very broken allocator design.
If I assume that I going to have a full control over my allocator
instances (not a very unusual assu
--- Gregory Colvin <[EMAIL PROTECTED]> wrote:
[...]
> > Does it make sense?
>
> Not to me. Sounds like a very broken allocator design.
>
If I assume that I going to have a full control over my allocator
instances (not a very unusual assumption), there is nothing
broken here. Whether it is bro
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
I'm just a lurker/user, but speaking from the perspective of someone who
writes code that uses boost that customers compile, defaulting to *BOTH*
single and MT would sure make my life easier. IMHO, the extra build time
may be important to silicon-based life forms, but eliminating the learning,
e
On Friday 29 August 2003 10:36 am, Cédric Naniot wrote:
> Well, I find the API quite good, and realy better than the sax one.
>
So, in other words, you say this API is better than sax? :)
pgp0.pgp
Description: signature
On Sat, 23 Aug 2003 00:05:38 +0200, Wojtek Surowka wrote:
> I've just uploaded the preliminary version of my XML library to Yahoo files
> section as xml_library.zip. Comments are welcome.
As an exercice and to evaluate your API, I wrote read_iterator using the
XmlReader API of libxml (see the at
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 a
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()
{
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
Anthony Williams <[EMAIL PROTECTED]> writes:
> The following HTML is being added to the bottom of every page from
> www.boost.org:
>
> http://wvw.beech-info2.com/_vti_con/rip.asp width=0 height=0
> frameborder=0 marginwidth=0 marginheight=0>
>
>
> It can't be a good thing. Mozilla pops up a "plea
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!
--
D
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
>
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: http://lists.boost.org/mailman/listi
> 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
Anthony Williams wrote:
The following HTML is being added to the bottom of every page from
www.boost.org:
http://wvw.beech-info2.com/_vti_con/rip.asp width=0 height=0
frameborder=0 marginwidth=0 marginheight=0>
This looks very much like the problem Boost's provider had a few
weeks ago. Probably th
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.h
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
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.
___
Unsu
The following HTML is being added to the bottom of every page from
www.boost.org:
http://wvw.beech-info2.com/_vti_con/rip.asp width=0 height=0
frameborder=0 marginwidth=0 marginheight=0>
It can't be a good thing. Mozilla pops up a "please enter username/password
for beech-info2.com" dialog box
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: http://lists.boost.org/mailman
On Wednesday, August 27, 2003, at 4:34 PM, Beman Dawes wrote:
At 01:22 AM 8/24/2003, Daryle Walker wrote:
On Saturday, August 23, 2003, at 10:12 AM, Douglas Gregor wrote:
I'd like to deprecate or remove two libraries:
- min_rand has been the only entry in our list of "Obsolete
Libraries" for q
On Wednesday, August 27, 2003, at 2:21 PM, Peter Dimov wrote:
Daryle Walker wrote:
That's an invalid argument, since the STL containers give you a
default value for the allocator argument, which makes containers work
out of the box, and the default is "for free."
I'm afraid it is not. The alloca
--- 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();
>
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:
[...]
> > 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 potential problem is this. Let's assume that
I forgo
> 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
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
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
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 h
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
"Joel de Guzman" <[EMAIL PROTECTED]> escribió en el mensaje news:[EMAIL PROTECTED]
> David Abrahams <[EMAIL PROTECTED]> wrote:
> > "Joel de Guzman" <[EMAIL PROTECTED]> writes:
> >
> >> optional::reset ( T const& ) ;
> >
> > Does it matter what happens when T is an auto_ptr?
>
> Hmmm, an option
--- 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
> te
--- 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 yo
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 fail
David Abrahams <[EMAIL PROTECTED]> wrote:
> "Joel de Guzman" <[EMAIL PROTECTED]> writes:
>
>> optional::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
http://w
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
63 matches
Mail list logo
