On Mon, Jun 23, 2008 at 6:14 AM, Bruno Haible <[EMAIL PROTECTED]> wrote:
> Arnaud Charlet wrote:
>> One possibility is to do what we do for Ada: have a style/coding checker
>> built into the compiler (C++ front-end) as a special switch, and enable this
>> switch during bootstrap, so that any such coding style violation is 
>> transformed
>> into an error
>
> Yes, this can be the technical implementation of limiting the set of C++
> features.
>
> Additionally, it needs to be avoided that the limits get pushed out year
> after year, allowing, for example, inline templates in one year, template
> member functions the next year, and complete template metaprogramming the
> year after that. To this end, it must be made very hard to extend this
> subset of C++. Possibly it should require agreement from the Steering Comittee
> to do so.
>
> Bruno

while `creative' uses of templates are certainly a problem -- we don't
really want
people to start writing clever (which most of the time means brittle)
codes, we should
also refrain from putting FUD on templates.  There is a subset of C++ templates
stable enough over the years, that can be used without fear,
uncertainty and doubt.

I don't see banning inline template as increasing the readability of
GCC codebase.

-- Gaby


>
>

Reply via email to