Hi Fernando,
- Mensaje Original -
De: Fernando Cacciola [EMAIL PROTECTED]
Fecha: Sbado, Julio 12, 2003 1:22 am
Asunto: [boost] Re: Interest in multiindex_set?(again)
Hi Joaqun,
Unfortunately, I douldn't compile the code with BCC because it
extensivelyuses non-type template
Hi Joaquín,
JOAQUIN LOPEZ MU?Z wrote:
Hi Fernando,
- Mensaje Original -
De: Fernando Cacciola [EMAIL PROTECTED]
Fecha: Sábado, Julio 12, 2003 1:22 am
Asunto: [boost] Re: Interest in multiindex_set?(again)
[snip]
Now, index_n.begin() and index_n.end() let you enumerate *all* the
The old input iterator 24.1.1 had a requirement:
*r++ returned type T, semantics {T tmp= *r; ++r; return tmp; }
The new Single Pass Iterators in N1477 have no such requirement.
That's fine with me - that requirement was a source of bugs in my code and
violated the rule of least astonishment
David Abrahams wrote:
That's because void_ is for MPL internal use only; it's not a type
you should manipulate
While I agree that _some_ user needs for a special unique type a
better handled by introducing a new one (otherwise you'll get yourself
into situation like we have right now, only in
Beman Dawes [EMAIL PROTECTED] writes:
The old input iterator 24.1.1 had a requirement:
*r++ returned type T, semantics {T tmp= *r; ++r; return tmp; }
The new Single Pass Iterators in N1477 have no such requirement.
That's because the requirement mixes access and traversal.
That's
Aleksey Gurtovoy [EMAIL PROTECTED] writes:
IMO we should just stop using 'void_' for internal purposes and give it
up to users :).
I am still unsure about 'void_' being better than 'nil' or
'null' Users already have a type, 'void', which means void.
There's no correspondence between void_
Hi again,
- Mensaje Original -
De: Fernando Cacciola [EMAIL PROTECTED]
Fecha: Sbado, Julio 12, 2003 7:32 pm
Asunto: [boost] Re: Re: Interest in multiindex_set?(again)
[stuff about conceptual structure of multtindex_set deleted]
OK, I'm glad we finally got to understand each other :)
David Abrahams [EMAIL PROTECTED] writes:
That's fine with me - that requirement was a source of bugs in my
code and violated the rule of least astonishment as far as I was
concerned.
But before I remove the test from the filesystem library that verifies
the old input iterator semantics for
David Abrahams wrote:
Aleksey Gurtovoy [EMAIL PROTECTED] writes:
IMO we should just stop using 'void_' for internal purposes and give it
up to users :).
I am still unsure about 'void_' being better than 'nil' or
'null' Users already have a type, 'void', which means void.
... in
On Sat, Jul 12, 2003 at 01:21:49PM +0100, Andy Sawyer wrote:
There's a third form I've also found useful on occasion:
struct selector1st
{
templatetypename Pair
const typename Pair::first_type operator()( const Pair a ) const
{
return a.first;
}
};
Which has the advantage
At 05:47 AM 7/12/2003, Daniel Frey wrote:
PS: Would it make sense to have a boost bug bashing week or something
to fix some more bugs/regressions? Or do we wait for users to complain
and provide fixes?
Until recently, figuring out which tests should pass for each compiler was
difficult.
That's because void_ is for MPL internal use only; it's not a type
you should manipulate (I think Aleksey doesn't believe me, but I'm
about to prove it... wink).
It's quite all right - my code does not use that other type, I just
need a type. I could have just as well used my own class
Hello,
I saw a lot of new regression runs on various platforms. One obvious
question: Should we remove the outdated runs?
Now for the real reason of this message: One compiler (the SGI MIPSpro)
complains (with a warning) about:
cc-1234 CC: WARNING File =
Edward Diener writes:
Andy Sawyer wrote:
Marshall's first and second are slightly different to the HP
versions:
template class T1, class T2
struct first: std::unary_function std::pair T1, T2, T1
...
vs.
templatetypename Pair
struct select1st
:
Fernando Cacciola wrote:
JOAQUIN LOPEZ MU?Z wrote:
[...]
Another thing I couldn't figure out is how to compose indices
hierachically.That is, how to reproduce a typical SQL SELECT *
ORDER BY X,Y,Z.
Since you're modeling an indexed table, this functionality should be
supported.
This is an
Aleksey Gurtovoy [EMAIL PROTECTED] writes:
David Abrahams wrote:
Aleksey Gurtovoy [EMAIL PROTECTED] writes:
IMO we should just stop using 'void_' for internal purposes and give it
up to users :).
I am still unsure about 'void_' being better than 'nil' or
'null' Users already have a
Beman Dawes [EMAIL PROTECTED] writes:
At 04:17 PM 7/12/2003, David Abrahams wrote:
A single-pass iterator is required to support r++ (inherited from the
incrementable iterator requirements), but I guess that we've
unintentionally dropped the requiremnt for *r++ of readable
David Abrahams [EMAIL PROTECTED] wrote:
Aleksey Gurtovoy [EMAIL PROTECTED] writes:
IMO we should just stop using 'void_' for internal purposes and give it
up to users :).
I am still unsure about 'void_' being better than 'nil' or
'null' Users already have a type, 'void', which means
Larry Evans wrote:
[snip]
I'm trying to get synopsis to translate into Boost guideline form;
however, I'm having trouble with getting comments properly attached
to the declarations. As soon as that is done, I'll upload it.
The comments are properly attached; however, the ASCII formatter
only
At 07:19 PM 7/12/2003, David Abrahams wrote:
Beman Dawes [EMAIL PROTECTED] writes:
At 04:17 PM 7/12/2003, David Abrahams wrote:
A single-pass iterator is required to support r++ (inherited from
the
incrementable iterator requirements), but I guess that we've
unintentionally dropped
Beman Dawes [EMAIL PROTECTED] wrote:
In the main CVS? iterator-categories.html is still dated several days
ago. Or am I looking in the wrong place?
I guess so. Why would I be editing a document in the multi_array lib?
I was talking about
Matthias Troyer wrote:
Dear Boosters,
After a recent cvs update I can no longer compile the boost filesystem
library:
The filesystem library was broken by the update in the main CVS to the
new iterator adapators library, and AFAIK the changes that are needed
have yet to be completed.
---
Joel de Guzman [EMAIL PROTECTED] writes:
Beman Dawes [EMAIL PROTECTED] wrote:
In the main CVS? iterator-categories.html is still dated several days
ago. Or am I looking in the wrong place?
I guess so. Why would I be editing a document in the multi_array lib?
I was talking about
On Saturday, July 12, 2003, at 9:21 PM, Joaquín M López Muñoz wrote:
Hi again,
- Mensaje Original -
De: Fernando Cacciola [EMAIL PROTECTED]
Fecha: Sábado, Julio 12, 2003 7:32 pm
Asunto: [boost] Re: Re: Interest in multiindex_set?(again)
[stuff about conceptual structure of multtindex_set
In another thread, by Joaquín M López Muñoz, there is talk of a helper
class like:
//
template
class Class,typename Type,
Type Class::*PtrToMember,
typename Compare=std::lessType
struct less_by
{
less_by(const Compare
25 matches
Mail list logo
