Re: Can we go ahead and run indent on our source?

Josh Wilmes:
> I'd like to go ahead and ask for
>   ./run_indent.pl `egrep '*\.[ch]$' MANIFEST | egrep -v \
>                    'global_setup.c|packfile.c|mops.c|io.h'`
> to be applied to CVS.

I'd rather not, to be honest; as you've found, indent is a useful starting
point, but it needs a human to follow up and make sure everything's the
clearest it can be.

> I've noted some glitches in indent's output, summarized below.  However, I 
> think it's easier to fix these afterwards than for me to try to mail a giant
> patch to the list.

If you're prepared to fix the output up manually, feel free to run indent on
your local copy, fix it up, and then mail me a diff; or we can get you commit
access.

-- 
The use of COBOL cripples the mind; its teaching should, therefore, be
regarded as a criminal offence.
		-- Edsger W. Dijkstra, SIGPLAN Notices, Volume 17, Number 5

• Can we go ahead and run indent on our source? by Josh Wilmes
• Re: Can we go ahead and run indent on our source? by Josh Wilmes
• Re: Can we go ahead and run indent on our source? by Simon Cozens
• Re: Can we go ahead and run indent on our source? by Josh Wilmes