On Sat, Nov 08, 2008 at 02:35:55PM +0000, Andreas Ericsson wrote: > Steve Frécinaux wrote: > > Just a random question: is there a reason why you have put all the > > .h in a separate includes/ directory instead of relying on the > > install target to put the include files at the right place ? > > To me it makes it much harder to hack on the files as one is always > > required to switch between both directories... > > I agree with this, but as I guess Shawn will do roughly 45 times more > work on it than me (according to current commit-count in git.git), I'll > live with it. I don't, modifying the public includes may break the ABI and the API. I believe it to be a good practice to put them in a separate directory so that people modifying them will know this particular header is public. Yes you can name your private headers differently, but it's not really the same, it doesn't make editing public headers hard, and it has to. People modifying them _have_ to thing "err why am I modifying this specific header in the first place" before doing anything in it. -- ·O· Pierre Habouzit ··O madcoder@xxxxxxxxxx OOO http://www.madism.org
Attachment:
pgpoWLu82JVYu.pgp
Description: PGP signature
