Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stdcxx.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: __rw_and (Was RE: Some internal aliases for
 __rw_integral_constant?)
Date: Thu, 26 Jun 2008 10:26:37 -0600
Message-ID: 
 <CFFDD219128FD94FB4F92B99F52D0A4901DB05F0@exchmail01.Blue.Roguewave.Com>
Thread-Topic: __rw_and (Was RE: Some internal aliases for
 __rw_integral_constant?)
Thread-Index: AcjXo9O0Yzj1XKB1RlqzZtgqwGKndAAAdbCA
References: 
 <CFFDD219128FD94FB4F92B99F52D0A4901DB05EA@exchmail01.Blue.Roguewave.Com>
 <48617F0F.2020100@roguewave.com>
 <CFFDD219128FD94FB4F92B99F52D0A4901DB05EB@exchmail01.Blue.Roguewave.Com>
 <CFFDD219128FD94FB4F92B99F52D0A4901DB05EC@exchmail01.Blue.Roguewave.Com>
 <4863B97C.7050304@roguewave.com>
From: "Eric Lemings" <Eric.Lemings@roguewave.com>
To: <dev@stdcxx.apache.org>

=20

> -----Original Message-----
> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of Martin Sebor
> Sent: Thursday, June 26, 2008 9:45 AM
> To: dev@stdcxx.apache.org
> Subject: Re: __rw_and (Was RE: Some internal aliases for=20
> __rw_integral_constant?)
>=20
> Eric Lemings wrote:
> > =20
> [...]
> > Okay, another proposal for inclusion though this particular utility
> > may be a stretch unless you understand variadic templates very well.
>=20
> Can you show what the code looks like w/o __rw_and for comparison?

I could try but you would want to read it about as much as I would want
to write it.  :)

Basically, it would require all the hackery required for simulating
variadic templates.  Not pretty.

>=20
> In general, an important design principle behind stdcxx is efficiency,
> both in time and in space. And in terms of time, both compilation as
> well runtime efficiency is important. In contrast to the ordinary
> kind, template metaprogramming tends to increase compilation times
> much more noticeably. In C++ 0x a good amount metaprogramming code
> is dictated by the standard already but as a rule we need exercise
> restraint when introducing templatized helper code, especially
> when template recursion is involved.

Right.  The way I see it, utilities like this are indended to simplify
the required metaprogramming code.  In order to do that though, other
developers would have to reuse it.  :)

That's why I said at the bottom of the email that I'll probably hold off
on moving it up the chain of includes to a more generic header where it
would be more reusable until such a time when other developers find more
need for it.  (I doubt tuples will be the only place requiring
compile-time logical operators.)  But it's posted now so we're all aware
of it at least.

BTW, is template recursion really costly in terms of compile times?

Brad.