🚀 go-pugleaf

John A Hughes wrote:

[snip]

> A file should contain exactly the header files it depends on, no more and
> no less. If removing a #include causes you to add it somewhere else, you
> were relying on a non-local and confusing inclusion structure anyway, which
> you should be thrilled to have exposed. And why should one expect changing
> a header file not to "break" code that includes it anyway?
> 
> I *hate* it when people give me libraries that insist I include something in
> order to include their file, or have to put includes in a certain order. It's
> stupid and unnecessary if you follow the simple rule above.

I agree. Here at Axon we also apply this concept to libraries.

Although a tool to ensure each #include is surrounded by the right 
#if's should be easy. The biggest trouble would be tracking which definition 
to use.

-- 
Andrew Dalgleish
Senior Software Engineer
Axon Research, Pty Ltd
6 Wallace Ave
Toorak, VIC
3142
AUSTRALIA
Tel:	+61-3-9826-5538
Fax:	+61-3-9824-0083
Email:	andrewd@axonet.com.au

      [ Articles to moderate: mailto:c++-submit@netlab.cs.rpi.edu ]
      [  Read the C++ FAQ: http://www.connobj.com/cpp/cppfaq.htm  ]
      [  Moderation policy: http://www.connobj.com/cpp/guide.htm  ]
      [      Comments? mailto:c++-request@netlab.cs.rpi.edu       ]