The ParseVariables() routine takes an error line (usually an
equation) as its argument and determines the values of any
variables in that line. This can greatly speed up debugging by
not having to enter specific debugging information lines for each
suspect line.

* Functions (eg, left(), strip(), etc) are not included in the printout
* All uninitialized variables will be put in a single line labeled LIT
* All variables, including those used in compound variables, will have
    their current value printed
* Variables will only be listed once

Because the routine must be able to query the values of the variables in
the suspect line, this routine can't be made a PROCEDURE. All variables
used by the routine, then, start with PV_ to (hopefully) prevent over-writing
variables used by the main program.

To see the results of this macro, simply open a shell and type

  rx <path>ParseVariables.rexx

Try changing the assigned variables and the "dummy" line to see other results.

Please let me (Ron Goertz <goertzearthlink.net>) know if this function is of
use to you, doesn't work for you, or if you have ideas on how to improve it.
This routine was developed for use in my calendar creator, FWCalendar: THE
calendar creator for Final Writer and PageStream.

 PERMSSN    UID  GID    PACKED    SIZE  RATIO     CRC       STAMP          NAME
---------- ----------- ------- ------- ------ ---------- ------------ -------------
[generic]                 1380    3269  42.2% -lh5- d8c6 Aug 14  1999 ParseVariables.rexx
---------- ----------- ------- ------- ------ ---------- ------------ -------------
 Total         1 file     1380    3269  42.2%            Aug 15  1999