Newsgroups: comp.os.msdos.programmer
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!news.cs.indiana.edu!maytag!watstat.waterloo.edu!dmurdoch
From: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Subject: Re: byte vs word movs
Message-ID: <1991Jun22.170522.3008@maytag.waterloo.edu>
Sender: news@maytag.waterloo.edu (News Owner)
Organization: University of Waterloo
References: <1991Jun21.031758.11264@cs.mcgill.ca> <ysyw42w164w@bluemoon.uucp>
Date: Sat, 22 Jun 1991 17:05:22 GMT
Lines: 16

In article <ysyw42w164w@bluemoon.uucp> andy@bluemoon.uucp (Andy Vaught) writes:
>storm@cs.mcgill.ca (Marc WANDSCHNEIDER) writes:
>> SECTOR    DB 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22
...
>> MOV  DX, SECTOR[BX]
>> 
>The above is perfectly legal. The problem is convincing MASM of its 
>legality. You might need an "OFFSET" keyword before "SECTOR". I don't 
>know, I use Turbo Assembler, which has much more rational syntax. 

What does it do?  The instruction looks ambiguous to me, since DX is word
sized and SECTOR[BX] is byte sized.  Does TASM move a word (i.e 0B0A if
BX=0)?  That's probably not what was intended...

Duncan Murdoch
dmurdoch@watstat.waterloo.edu