RE: Strange behavior w/%editc()

On Thursday 28 February 2002 2:23 am, Joe Pluta wrote:
> > From: James Rich
> >
> > 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 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. Perhaps you intuit it from the source?  Now
> THAT would truly be an awesome skill.
>
> Joe

Hi Joe

Not so awesome if it's in your coding standards ;-) We tend to use the
PREFIX keword to add an identifier to file fields which does help a lot.
Another thing that helps (me, at least) is defining program fields in
mixed case and file/external fields kept in upper case. Admittedly it's a
bit more effort to do specific case coding so I wrote a program (as you
do) to tidy up the code to match the our standards.

This style obviously doesn't get you the full detail available in a
compile listing, but I generally only refer to a listing now to sort out
compile bugs ;)

Regards, Martin
--
martin@dbg400.net  jamaro@firstlinux.net  http://www.dbg400.net        /"\
DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open        \ /
Source free test environment tools and others (file/spool/misc)         X
[this space for hire]  ASCII Ribbon Campaign against HTML mail & news  / \