Re: Compile error when using field in a subfield data structure

Thanks for the thoughts and I agree with most of them. I spend many hours 
cleaning up old application code as I install new functionality and I will 
agree 
that some indention helps but I find that vertical spacing and written 
comments adds much more to the reading of the code. In my opinion, if my coding 
companions knew how to write a good newspaper article they would do a better 
job of 
producing code that was both well designed functionally and easier to read.

Some time ago I used a documentation package that ran on a Windows platform. 
The interesting thing that you could do with "All Clear" was to extract the 
comments out of the code source and produce flowcharts. So it has been habit 
now 
to use the rough rule and if the total line count is not 50% comment the code 
is under documented.

In the past I have worked on the generation of compiler code so I know how 
frustrating and under appreciated your work can seem but we need you all to 
keep 
pushing back the frontiers of ignorance even if we will continue to bitch.

Folks talk about taking away the Move opcode as a negative aspect but in my 
world taking away the use of right hand indicators *INxx is just as bad. BIFs 
may have some definite advantages but don't expect all of us to agree without a 
fight.

Thanks again for your kindness to answer my bitches in a kind way and we both 
know that we have the best platform to work with and lets hope that someone 
will continue to sell it with gusto and not just rename it.

Thanks,
Jack Derham
Direct Systems, Inc.