From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <7871fcf50610220937g58fcaa04yfa995a524ab4ae0f@mail.gmail.com>
Date: Sun, 22 Oct 2006 12:37:12 -0400
From: "Joel Salomon" <joelcsalomon@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Include guards and multiple includes
In-Reply-To: <CB60E5CD-5335-41F1-949C-7E4F74ACD84A@telus.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <219D85AA-959D-464C-90C2-0F132809F0B9@telus.net>
	<7871fcf50610201227s17987c4at9bafba8729f8a6b9@mail.gmail.com>
	<ee9e417a0610201318o469eeec9lacd7c7ed2924fcc1@mail.gmail.com>
	<CB60E5CD-5335-41F1-949C-7E4F74ACD84A@telus.net>
Topicbox-Message-UUID: d1808e18-ead1-11e9-9d60-3106f5b1d025

On 10/20/06, Paul Lalonde <plalonde@telus.net> wrote:
> Ah well, there goes one argument for keeping the header soup clean.

A better argument comes from a recent post on comp.lang.c:
"automatically remove unused #includes from C source?" where the
fellow asks for a tool to automatically analyze C source to find these
unused includes.

--Joel