I just released version 2.1 of LLF, so watch out. There were a number of
bugs in the cross-reference feature which should have caused an acc-vio
failure or at least jibberish to be printed if anyone had asked for one.
There is also a bug in the VAXC optimizer that I haven't been able to
isolate which may have caused some unusual problems. The latest version is
compiled with that level of optimization removed (so far, no problems).

The two most visible changes with this version of LLF are the sticky
directories on the input filenames and the FILE and LIBRARY commands
in the option file.

The sticky directories behave exactly the same as all the other VMS
commands; subsequent files in a list inherit the node, device and
directory of the file preceeding it. For instance:

	$ LLF one,fred:two,three

the file "three" inherits the device and directory specified by the
logical name "fred:" on file two. If you don't want that, you need
to say:

	$ LLF one,fred:two,sys$disk:[]three,four,...etc.

the SYS$DISK:[] will restore the default to the current default directory.

The FILE and LIBRARY commands in the option file allow for you to get around
the 1024 character limits placed on the DCL command line input. You can
specifiy as many files as you need and they will be processed in the order
that they appear in the FILE/LIBRARY directive(s) and also in the order
in which the option file appears in the command line input. For example,
an option file named FRED.OPT contains:

	FILE ( one.ol two.ol )
	LIBRARY ( three.lib )
	FILE ( four.ol )

and a command input of $ LLF five,fred/opt,six will process the files
in the following order:

	five,one,two,three/lib,four,six

As with command input, the default file types of .OL, .OBJ or .LIB will
be used on the files specified in the option file and the sticky directories
behave the same as on the command line except the directories are not
remembered across FILE or LIBRARY directives (i.e. each new FILE directive
starts with a default of SYS$DISK:[]).