[Info-vax] Source Code Formatting (was: Re: Fortran)
Stephen Hoffman
seaohveh at hoffmanlabs.invalid
Fri Dec 7 18:35:05 EST 2018
On 2018-12-07 22:45:22 +0000, Dave Froble said:
> As for automatic formatting, I'm sure it can be helpful, but I'm a bit
> set in my ways, and prefer the formatting I've developed through the
> years. Perhaps a personal preference.
The IDE I'm working with gets rid of the need to deal with the
formatting for most source input—it's surprising how nice automatic
source code input (re)structuring can be—and the reformatting tools
also mean I can reformat code arriving from others.
The astyle tool and clang formatter both support various formats,
meaning most folks can be happy with what they can get.
Yes, source code metrics tools that don't mask whitespace can get
tangled. Which is part of why I usually recommend using a formatter in
the source code control checkin path.
Editing source code in EDT and LSEDIT can be comparatively more work,
as compared with some of the newer development tools. Yes, the newer
tools can be much more complex, too.
For those using vim, emacs editors, there can be options. Including astyle.
https://stackoverflow.com/questions/2355834/how-can-i-autoformat-indent-c-code-in-vim
I hadn't ever expected to be using an IDE, either. Some IDEs and a
number of the early IDEs were... bad.
--
Pure Personal Opinion | HoffmanLabs LLC
More information about the Info-vax
mailing list