Xref: utzoo comp.lang.c:34229 comp.os.msdos.programmer:2108
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!nosc!cod!bmarsh
From: bmarsh@cod.NOSC.MIL (William C. Marsh)
Newsgroups: comp.lang.c,comp.os.msdos.programmer
Subject: Re: warning to users of INDENT.EXE
Message-ID: <2489@cod.NOSC.MIL>
Date: 26 Nov 90 19:15:15 GMT
References: <73542@iuvax.cs.indiana.edu>
Reply-To: bmarsh@cod.nosc.mil.UUCP (William C. Marsh)
Organization: Naval Ocean Systems Center, San Diego
Lines: 17

In article <73542@iuvax.cs.indiana.edu> bomgard@iuvax.cs.indiana.edu (Tim Bomgardner) writes:
>I recently inherited a large multi-file c program with little or no
>visual structure (indenting, whitespace, etc.).  I ran it all thru
>indent.  A couple days later I discovered indent had made some
>unauthorized changes.  In particular, all statements that were
>originally in the form

Funny, I had just been given a task to find this problem.  It seems that the
latest version of indent (I got it from uunet) has this fixed.  I guess one of
the original purposes was to convert older C code.

Bill
-- 
Bill Marsh, Naval Ocean Systems Center, San Diego, CA
{arpa,mil}net: bmarsh@cod.nosc.mil
uucp: {ihnp4,akgua,decvax,dcdwest,ucbvax}!sdcsvax!nosc!bmarsh
"If you are not part of the solution, you're part of the problem..."