Tom Tromey wrote:
Dan> It also has almost zero hope of working over multiple compiler versions,
Dan> being future proof in general, and not having other compiler vendors
Dan> fight over message number namespace.
The maintenance issue is a major one. This document definitely needs
to address this, and not just in some theoretical way. Otherwise,
chaos ensues. I'm sure we've all seen the consequences here plenty of
times, enough to insist on a solution
Yes. When I update this proposal, I'll include more details. However, I
do not have extensive experience crafting such specs so any guidance
is very helpful.
One thing I am not very clear about myself in this discussion. Is
optimization
diary a life time GNU extension ? Or Is it suitable enough to prepare a
proposal for inclusion in future DWARF version ?
-
Devang
