Re: [v3] enum consistency, __num_base cleanups

[Phil Edwards <phil at jaj dot com>]

On Thu, May 08, 2003 at 11:37:24AM +0200, Gabriel Dos Reis wrote:
> 
> The short answer is:  They are not supposed to read the implemntation. 

You've misunderstood.  Please read it over again.

> I would oppose to any change from the implementor's name space to
> anything else.

Gaby, give me some credit here.  I'm not proposing anything that stupid.

> If HTML don't display
> "nicely" underscores, fix the tool to remove the underscoe.

The tool cannot be "fixed" because it's working just fine... it's designed
for users, after all, not library implementors.  The tool will let us
compensate for the extra _'s like this:

  ---A----   -------B--------   -----C-----
  | real |-> | filter which |-> | doxygen |
  | code |   | removes _'s  |   |         |
  --------   ----------------   -----------
            
Right now, we go from A to C directly.  Step C will actually perform step
B for us once B exists.

B does not affect A.  The arrow does not point backwards.

However, B is quite difficult without a known set of names.  And that's
the change I'm planning.

E.g., instead of _T, _Tp, _Type, _TypeName, etc, all through the vector
code, we pick one and use it.  Same for _T2, _Tp2, _SecondType, whatever.
Likewise for _Iter, _Iterator, _It, and whatnot though the algorithms code.
The names should remain descriptive, and we can still have an infinite number
of them, but I'd like to be able to easily predict them or look them up or...


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams