From: kilo a. G. K. <kg...@gm...> - 2012-09-20 20:50:18
|
Hi Jean-Philippe, On 20 September 2012 15:46, <jpm...@fr...> wrote: > Well, Kilo, I don't understand your using these "full" paths scheme for includes, > like "#include "src/drivers/kilo2008/kdriver.h", I had a serious 2-day halt on a header file location issue sometime back in early 200X, so whenever I read about this it always comes to my mind to do something to prevent it. Some even argue if you should put header files in the same dir as c/cpp files but move them to a separate include dir... eg Linux > If no actual need, but only an "aesthetic" will ... I'd argue that > these "full" include paths make you code less reusable (by copying), > more difficult to read ... and not following the C coding "standards" > (I've never seen this kind of thing in the multiple C/C++ codes > I've dealt with over the passed 17 years). OK, I'll submerge now into my hidden caves and gain more power in secret - but do fear my return one day when I'll include with a path!!! (dramatic music getting louder and louder, satanic laughter and a horrible fiend playing an enormous organ) :D:D cheers kilo -- http://three.sentenc.es |