Literal cross-reference objects

[MacWheel99@xxxxxxx]

When modifying a BPCS program, often heavily filled with L number strings, it 
can be very time consuming to be looking up what this literal or that one 
signifies, so that I can understand what a section of code is working with 
before I make any changes.  When there are enough of them, I might remember 
that I looked up this one before, but not what it was.  The way the object 
technology plays out, a compiled program does not offer a convenient 
reference list of literals used in it, unlike textual clues in the naming of 
data fields associated with various files & other structures, with decent 
associated labeling.

A slick tool I am sure we could use is to run some source code against the 
literals message files & get an abbreviated reference list - here are all the 
literals used in this program, the associated text, and a few other values.

An even nicer feature might be a post-compiler which mucks with the IBM 
compiler print-out & inserts in a blank space column (if any practical 
available) the significance of literals on that line, or possibly safer, 
inserts a new line just after a line using a literal ... what the heck it is.

Lazy Al
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---