Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!timbuk!cs.umn.edu!kksys!wd0gol!newave!john
From: john@newave.UUCP (John A. Weeks III)
Newsgroups: comp.sources.wanted
Subject: Re: Source Code Cruncher
Keywords: Source Code
Message-ID: <536@newave.UUCP>
Date: 2 Dec 90 20:29:58 GMT
References: <111@atc1.UUCP>
Reply-To: john@newave.mn.org (John A. Weeks III)
Organization: NeWave Communications Ltd, Eden Prairie, MN
Lines: 20

In article <111@atc1.UUCP> shyam@atc1.UUCP (Shyam Mittur) writes:
> I have a requirement to take lots (many hundreds of thousands of lines) of
> C code and crunch it down to the smallest size possible that would build
> correctly.  Among the things I anticipate doing are: Stripping off comments
> and blank lines, rearranging indentation, replacing variable and function
> names by short but unique names, and so on.

Out of curiousity, why would you want to do such a thing?  I can understand
wanting to shroud a program, but what you are proposing to do will result in
code that is difficult to maintain and possibly confusing to the compiler, not
to mention the risk of introducing new subtle bugs and the rath of Henry's
8th commandment.

-john-

-- 
===============================================================================
John A. Weeks III               (612) 942-6969               john@newave.mn.org
NeWave Communications                 ...uunet!rosevax!tcnet!wd0gol!newave!john
===============================================================================