Re: Has the time come to get rid of the "delivering" of public headers?

> I must say, of all the options so far, that one sound the most appealing to me.
> and it can be done 'incrementally', one module at the time...

One could do the thing I suggested incrementally, too.

> While we are at it, why not have just one public header file per
> module...

But isn't this "module" terminology mostly wishful thinking in many
cases? I.e. some "modules" contain stuff that are not really related
much at all from a functionality point of view, and in other cases
stuff that one would imagine belongs together has been split into
several "modules" for obscure and/or obsolete reasons.

--tml