Boost logo

Geometry :

Subject: [ggl] plan
From: Bruno Lalande (bruno.lalande)
Date: 2009-04-22 04:36:56


> If you'd agree, I'd suggest to use upper-case for template parameters
> only, otherwise it's hard to decipher what is what when reading through
> code and requires to go back up to function/type prototype to find out.

Oh I wanted to talk about that, and had finally forgotten. I
personally think that UPPERCASE should only be used for macros and
constant literals, BTW I wonder if there's not a Boost guideline or
implicit rule prohibiting the use of UPPERCASE in any other context.
In Boost, typedefs are usually in lower_case like you did (exactly
like types, which is consistent) and template parameters are
UpperCase. That's why concept names are usually UpperCase as well in
the docs, since they end up as template parameters in the code. What
do you think about all that?


Geometry list run by mateusz at