Sender: bill AT taniwha DOT tssc DOT co DOT nz
Message-ID: <36F895CF.1612CA0D@taniwha.tssc.co.nz>
Date: Wed, 24 Mar 1999 19:35:43 +1200
From: Bill Currie <bill AT taniwha DOT tssc DOT co DOT nz>
X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.2.3 i486)
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
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> <199903231517 DOT KAA15891 AT envy DOT delorie DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

DJ Delorie wrote:
> 
> > 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.

Hmm, pretty easy to do, and seams to be a resonable idea (more info to
the programmer is good).

ob sh[lr]dl: It seems to me that you (DJ) agree sh[lr]d should not be
overloaded (I hate mul (imul?) for that), but I don't think I've ever
been entirely happy with sh[lr]dl.  It can be used in both 16 and 32 bit
modes (determined by the register, thankfully always present) and I
think the name is slightly confusing with that 'd' in there (is that
what you meant by vague earlier?).  sh[lr]l didn't work for me either. 
If anybody comes up with a good mnemonic (or we decide that overloading
a mnemonic isn't so bad, but I *really* don't like that, assembly can be
confusing), I'll make the change.

Hmmm, what about lshr[lr]?  (just hit me)

Bill
-- 
Leave others their otherness.