>>>>Beautify is your friend!
>>>
>>>Yes, it is, until you work for someone who wants the ending commands to be indented.
>>
>>WHY does anybody get the right to demand how something as trivial as this has to be done? Power corrupts.
>
>Mike,
>
>I'd say you've never worked as staff in a mid-sized or large corp.

You and I worked at STN with a large group and there were no such standards that I can remember. I've seen a bunch of places where Rushmore understanding was lacking. Imagine if the standards prevented Rushmore. Why not focus on technical proficiency instead of style?

I never did big iron cobol.

>
>Many laugh, but the "Procedure Division" of a COBOL program *can* be a beautiful thing - flowing English that is easy to understand (even for non-programmers).
>HOWEVER, virtually every corp has turned it into a nightmare of ugliness and difficulty to read. There are standard prefixes/suffixes for 'memvars' and field names, etc. etc. as well as mandatory column alignment in the Procedure Division. Rules for virtually everything!
>
>DorrisB's example is extreme to me too. To me there is undoubtedly a requirement for some standardization in 'team' (oh, how I hate that word) environments.
>
>As an aside... I've never used Beautify in my life.

I showed Drew Speedie how instead of manually doing changing tabs to two spaces he could use search and replace. He was completely amazed that he didn't know that one.

Nobody knows everything. But what a shame that someone as brilliant as he was would WASTE oodles of time on such trivial matters.