From mboxrd@z Thu Jan  1 00:00:00 1970
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <219D85AA-959D-464C-90C2-0F132809F0B9@telus.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
From: Paul Lalonde <plalonde@telus.net>
Date: Fri, 20 Oct 2006 11:45:37 -0700
Subject: [9fans] Include guards and multiple includes
Topicbox-Message-UUID: cf13410c-ead1-11e9-9d60-3106f5b1d025

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm trying to convince some non-believers that include files should  
not include other include files, and that instead they should state  
their dependencies; they want hard data before they commit to such a  
scheme.

Is there some study kicking around that I could point them at rather  
than re-factor our code base and time the resulting builds?  I know  
the plan9 headers largely follow this pattern.

Paul

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFFORlRpJeHo/Fbu1wRAlExAKCsTZtCcW9FlqvUwllBye9EgRGqGwCgnYZn
0QcMNw3eC6a/3/XINvcD/Qw=
=H755
-----END PGP SIGNATURE-----