Environment variables
~~~~~~~~~~~~~~~~~~~~~

1. Variables to control compilation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1.1 TMP
    TEMP
    EON_TMP

    Where to place temporary files. Each of these is tested in turn. If
  	none are found temporary files will be placed in "/tmp" for Unix
	systems and the current directory for MSDOS.

	For example: TMP=/tmp

1.2 EON_COMPILER

    Select the C++ compiler to be used. This will override the use of
	the default "eon.cfg" file.

	For example: EON_COMPILER=gnu
  
1.3 EON_LIMITED_MEM	(MSDOS ONLY)

    On machines where system resources are limited, problems may occur.
	This option attempts to limit the use of resources by closing files
	when they are not need and reopening later.

	For example: EON_LIMITED_MEM=1

1.4 USER (MSDOS ONLY)
	
	The database tracks the user responsible for creating classes. On
	single user MSDOS machines, this variable allows a name to be 
	specified.

1.5 EON

    Specify the location of the Eon/Eiffel Universe.

1.4 EON_NO_UNIX_ARGS (MSDOS)

    By default the various Eon/Eiffel tools understand Unix style
	command line options, for example:

	eon -v1 file

    set EON_NO_UNIX_ARGS=1

    changes this behaviour and forces the use of / switches 


2. Variables to control system execution
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2.1 EON_TRACE
	
    Enable function tracing at runtime. This assumes the system was 
	compiled with TRACING turned on). This variable has two levels,
	1 and 2. Level 1 will only display function names. 2 will display 
	the contents of parameters passed to functions. See the section 
	on DEBUGGING

2.2 EON_ASSERT

    Enable assertion checking at run time. This assumes the system
     was compiled with the relevant assertions turned on. This variable
	can be set to a number of different letters, (r, e, i, l, c, n and a).
	For example:

	EON_ASSERT=rei
	EON_ASSERT=reilc
	EON_ASSERT=a
	EON_ASSERT=n

	These are explained in the section on DEBUGGING.
    

2.3 EON_DEBUG

    Enable debugging statements at runtime. This assumes the system
	was compiled with DEBUGGING turned on. See the section on 
	DEBUGGING.




 
