RE: Strange behavior w/%editc()

[James Rich <james@xxxxxxxxxxx>]

On Wed, 27 Feb 2002, Joe Pluta wrote:

> > Wow!!  You know what the variables are and where they come from without
> > the program source ?!?!?!  That is an awesome skill.  :^)
>
> Not really.  I use a compiled listing.  In my experience a compiled listing

Oh.  I was making a (not too funny) joke.  I thought maybe you
deconstructed the executable to get the variable names since you didn't
have the source.  If you have the source you can make a compile listing,
but no source...

> is different than the program source, and contains all the information I
> need.  You've said you don't like compiled listings.  I wonder how you get
> that same information - for example, which fields are from database files.

I think what I said was that I dislike having to resort to a compile
listing to find out what the variables are.  I'd rather that the code
itself was clear enough that an outside the source reference was not
needed.

But you bring up an excellent point:  how do people keep database, screen,
printer, and internal variables straight?  Even using a compile listing it
is sometimes difficult to remember where everything comes from.  I've
solved this problem with variable naming convention:  all externally
described fields are in all caps, fields from the same file must begin
with the same prefix, screen fields must begin with DF, printer fields
must begin with PF.  Following this convention we do "divine" variables'
definition locations by just looking at the source code.  But modifying
old code written before the standard is a PITA.

As regarding coding preferences, it is interesting to note that my boss
*loves* compile listings.  He prints out everything.  We work side by side
all day and he hasn't fired me yet!

James Rich
james@eaerich.com