Re: Bloat

>> In fact, I'd like to see a policy where we require a measurement and
>> evaluation of the benefit of introducing new inlines or "clever" cpp
>> trickery. (no, benchmarks run on vaxen don't count).
>
> Why not?
I've considered this. We're really need to move toward modular and
stable ABI. OTOH we may need tricks to run programs faster on slow
computers (older computers, embedded low-power processors, etc.).
It'd be a good compromisation to make important APIs a function by
default, while preparing a way to make them "optimized" for speed
(inline, less indirection, etc.). In the "optimized" case, ABI is not
kept. So users can choose either ABI or speed.
Masao