A 6 8 K	  M A I	N T E N	A N C E	   H I S T O R Y


Version	1.00 (Charlie Gibbs, June 18, 1987) - initial release


Version	1.01 (Charlie Gibbs, August 20,	1987)

	The following bugs in version 1.00 have	been corrected:

	      -	Long-word constants and	storage	areas were being
		aligned	on a double-word boundary.  The	only place
		where double-word alignment is now forced is at	a
		break between SECTIONs,	since the length of an
		AmigaDOS hunk must be a	multiple of 4 bytes.
		(CNOP 0,4 can still be used if double-word
		alignment is desired by	the programmer.)

	      -	If a label on an END statement or the first statement
		of a SECTION was named in an XDEF statement, it	would
		not be written to the object code file.	 The latter
		case includes both the label of	a SECTION directive
		and the	label of the first executable instruction in
		the absence of any SECTION directives (defaulting to
		an unnamed CODE	section).  In the final	case (default
		unnamed	CODE section), references to XREF symbols
		in the first statement would also not be written
		to the object code file.

	      -	If the last statement in the source file was not
		terminated with	a newline character (premature EOF),
		it was being ignored altogether.

	      -	A register list	as the source operand of a MOVE
		instruction was	not being flagged as an	error.
		(MOVE to a register list was being flagged, however.)

	      -	MOVE from USP was generating incorrect code.  Also,
		MOVE from SR or	CCR to an address register was
		generating incorrect code rather than being flagged.


Version	1.02 (Charlie Gibbs, September 9, 1987)

	The following bugs in version 1.01 have	been corrected:

	      -	Duplicate labels were not being	flagged.

	      -	XDEF symbols were not being dumped to the
		object code file when the -d option was	set.

	The following enhancements have	been added:

	      -	A header file is now supported.	 If the	parameter
		-h<filespec> is	included on the	command	line, the
		specified file will be included	as if the source
		module's first line was " include <filespec>".
		The file specification may include a path name,
		although the include path names	given by the
		-i parameter (if any) will also	be searched.

	      -	An equate file can now be produced.  If	the parameter
		-e<filespec> is	included on the	command	line, a	file
		will be	written	containing EQU statements for any
		symbol whose value is absolute.	 If -e is specified
		without	<filespec>, the	name of	the file will be
		formed in the same way as the list file, except	with
		an extension of	".equ".

	The following changes have been	made to	existing logic:

	      -	No symbol table	dump will be produced unless the
		-x (cross-reference) switch is set.  Formerly a
		symbol table dump was always produced, with only
		the cross-reference portion optional.