Journalling of aprepro!

Commands using aprepro statements are now journaled.  For example, "bri x {2*5.0}" is now journaled as "brick x {2*5.0}"
if "journal aprepro" is on, or "brick x 10" if "journal aprepro" is off.  The default is on.

In case you couldn't tell, there is a new command: journal aprepro [on|off].  If you don't specify on or off, the current
setting is displayed.

Some other important changes go along with this:

1) Comments are now journaled.  That's so you can get aprepro variable definitions journaled.

2) Numbers are journaled exactly as they are entered.  That means the maximum number of significant digits is determined
by the command input, not by a set number hard-coded into CUBIT.

3) When journal aprepro is off, numeric results of aprepro statements are journaled according to the rules currently in
effect.  In other words, the maximum number of significant digits IS hard-coded into CUBIT, using the value of DBL_DIG.

4) {Loop}, {If}, and other conditional aprepro statements are not currently journaled.  Instead, the commands are
journaled as they are executed, just as we have been doing up until now.  I'll get this working in the future.

5) Comments on the same line as a command get split into two separate lines in the journal file.  In other words, "bri x
1 # Make a brick" is journaled as:
brick x 1
# Make a brick

I'm excited about this checkin.  In the world of cut-and-paste journal file creation, this has the potential to save a
LOT of time and headache.  There have been many times that I used something like {Vx(35)} but saved it in my journal file
as the actual coordinate.  Later, when I made changes, it was a pain to figure out where that number came from.


- Darryl Melander, 9 March 2001