ludovic.cour...@inria.fr (Ludovic Courtès) writes: > What about sticking to the current “API” instead, and explicitly marking > as internal those parts that core developers know are still in flux? > > For instance, I would expect a large subset of <tree.h> and <cgraph.h> > to be stable (it’s been the case in my experience between 4.5 and 4.7.) > The rest can be tagged with a special convention (for instance, an ‘i_’ > prefix), to make it clear that it’s only meant for internal consumption.
This is an interesting goal but it is essentially impossible to implement. In both theory and practice, it's all in flux. GCC has been around for 25 years. Everything has changed in that time, and most things have changed multiple times. We do not want plugins to constrain internal development. So if we adopted your approach, the only honest option would be to mark everything as internal. And that would leave us where we are today. Ian
