On Sunday 24 May 2009, Zach Welch wrote: > > I'd suggest instead creating a > > new include/ area to hold only files which will be getting > > commitment for such public usage. > > This is common and I suppose that I should have listed it (to be fair), > but I am not a particular fan for the fact that it splits the interface > and implementation into different trees.
Well, yes ... what eventually goes into /usr/include should be strongly limited to the interfaces. How anything gets implemented inside the library is nobody's busienss except for the library maintainers'. They should be able change how they do things easily. But that won't happen if all kinds of random implementation detail are cast in concrete as part of the public /usr/include interface to the library. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
