Date: Tue, 23 Mar 1999 10:17:12 -0500
Message-Id: <199903231517.KAA15891@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <36F75A7B.412676A6@taniwha.tssc.co.nz> (message from Bill Currie
	on Tue, 23 Mar 1999 21:10:19 +1200)
Subject: Re: djasm shift semi bug + proposal
References: <36F5CF26 DOT AEED9A67 AT taniwha DOT tssc DOT co DOT nz> <199903221509 DOT KAA00687 AT envy DOT delorie DOT com> <36F69D7F DOT 25F23B74 AT taniwha DOT tssc DOT co DOT nz> <199903221957 DOT OAA32392 AT envy DOT delorie DOT com> <36F75A7B DOT 412676A6 AT taniwha DOT tssc DOT co DOT nz>
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Not a problem there: will `parse error' do?  djasm already does that due
> to it's design (great feature, that, though sometimes a parse error can
> be rather uninformative).

I'm thinking add the patterns for the "wrong" syntax, and have them
print errors warning people about the confusion.