====
-- RunReporter::minor bug fix in creating $GRED
-- fix for decrementing free variable. (see freevariable.cc:increment())
-- fix for RealValue::is_equal (check sign in difference)
-- fix for RealValue conversion to string. Used to have the default 
   precision of 6 (sprintf family), and small numbers (eg., 0.00000025)
   would appear to be 0.

==== from batch8 to batch9 		12/27/93

class Exp:: Reporter change:
    - from a hash table to a Stq in Exp::

==== from batch7 to batch8

synchronization with TransmitGUI:: uses the same code.
    - added code to Report class interface to support external reporter.

major bug fixes:
    - Stq::remove fixed
    - Exp::gettoolnum fixed to return the correct number.

cleanup::

==== from batch6 to batch7

- No MORE FreeVar: Replaced by FreeVariable inheritance structure.

- FreeVariableGroups:
    - ability to vary parameters in lock-step.
	
	VARY tool1.var1 FROM 10.0 to 20.0 BY 5.0
	VARY tool2.var2 FROM 100.0 to 125.0 BY 1.0
	VARY TOGETHER tool1.var1 AND tool2.var2

      the sequence would look like this:
	  
	  10	100
	  15	101
	  20	102
	  20	103		<< note how tool1.var1 gets locked.
	  20	104
	  20	105
	  ...
	  20	124
	  20	125

- Subclassing FreeVariable to various interesting ones, and especially now
  supporting ALL datatypes, such as TEXT.

    - LoopVariable: (EXISTING)
	
	VARY tool1.var1 FROM 10.0 to 25.0 BY 5.0

    - SetVariable: (NEW)

	VARY tool2.var2 SET one, true, three, four

      tool2.var2 is obviously of TEXT type or some ENUMERATED type.

- Mixing Groups with Non-Groups
	
	VARY tool3.var3 FROM 1 to 3 BY 1

	VARY tool1.var1 FROM 10.0 to 20.0 BY 5.0
	VARY tool2.var2 FROM 100.0 to 125.0 BY 5.0
	VARY TOGETHER tool1.var1 AND tool2.var2

      the sequence would look like this:
	  
	  1	10	100
	  2	10	100
	  3	10	100
	  1	15	101
	  2	15	101
	  3	15	101
	  1	20	102
	  2	20	102
	  3	20	102
	  1	20	103		<< note: tool1.var1 locked at 20
	  2	20	103
	  3	20	103
	  ...
	  1	20	125
	  2	20	125
	  3	20	125

==== from batch5 to batch6

Ability to extract variables, not just filenames, from previous tools in
the sequence:

consider the following sequence:
    seed -> source -> trace1 -> trace2 ....

now SEED has an OUTPUT variable called ``newseed'' and SOURCE has an LINK
variable called ``seed'' that is LINKED to ``seed.newseed'', and the type
is real.

Now EXCON is smart enough to execute the method (probably $RUN) specified
by the OUTPUT variable ``newseed'' to extract a real number and that gets
propagated to ``source.seed''.


CONS:
since there is a potential for each program wanting some result from its
previous one that is not being propagated via LINKED files (such as
spectrum from transmit into XLith), each individual tools must be executed
separately by the Exp::run method, and examined for extraction variables.

Until now, the entire sequence will be bunched in a ``Job'', and passed
onto the Job manager, which will execute the ENTIRE iteration in 1 shot
via shell script; now, each call to JobMgr::execute consists of one and
only one tool executtion description. This precludes parallel execution,
since the management gets hairy.

==================
