Re: InFormatter...the 4gl formatter

In article <E5A3nM.uG@news.nsw.CSIRO.AU>, Peter Wiley <peter@prospect.an prod.csiro.au> writes >In article <5dg889$j57@cssun.mathcs.emory.edu> timhood@bigfoot.com writes: >>I've written (many, many moons ago) an Informix 4gl formatting program. >>It works rather well, but I've created a list of enhancements that I >>would like to do to it. I'm wondering: >> > >[snip] > >Sorry, Tim, but I've always coded in rigorous style for readability. > >When I was "elected" project manager for our last project, the first thing >Christina & I did was write a definitive style guide. We simply don't >accept code from anyone that doesn't comply, regardless of whether they're >staff or contractors. > >I think what you're doing is providing a crutch for sloppy programmers. >I'd prefer they did it right in the first place. > >Regards, Peter Wiley I'd rather not waste time lining up blocks of code because they do not comply to a standard - I'd rather spend time designing, testing and debugging. I bet when the first C compiler came about the assembly language programers called it "a crutch for sloppy programmers"! So are debuggers after all you can get every thing from a hex dump of the binary. Code formatters are just another tool to reduce syntax complexity and let you concetrate on the sematics of the code. Plus there is no need to waster time checking that the code corresponds to the defined standard - just put it throught the code formatter as it gets checked back into version control. I can code using the formatting I prefer - alyput style is a subjective thing not objective and makes no difference to the final executable. -- David Williams