I've thought of how to phrase it.
Yes n3515 does allow more than the 'hard-typedef', they do (in part) do
the same job, but the context where you'd use one and not the other is
very clear, I like clean notations, I think that's a mathematician
thing, as I am sure you know (or have touched on) the mathematicians go
to great lengths to save themselves ink. I can think of many examples of
this, think of ways of writing integrals, especially ones along a
parameterized curve in a vector field, it just became an integral with
the symbol of the curve below it. 1 doesn't mean 1 it means the
multiplicative identity element of a set, "" 0 but for additive
notation. You get the idea (I don't want to bore you or go beyond) but
think of the hard-typedef as the integral symbol with a circle though
it, showing over a closed curve, it's just a short hand in a case where
you are integrating over a closed curve, the hard-typedef is a short
hand in the case you want to 'inherit' operations from the base class.
I hope this explains it better!
Alec
On 28/01/13 02:38, James Dennett wrote:
n3515 is also explicit that the permitted conversions have no run-time
cost. Is there anything that you propose that a "private opaque alias"
from n3515 does not provide? -- James
