[M3commit] CVS Update: cm3

[Tony Hosking]

Changes coming that should make life easier...

(HIstorically, the representation was BITS 16 FOR [0..16_FFFF] instead of the current BITS 8 FOR [0..16_FF])

On 10 Feb 2010, at 11:22, Jay K wrote:

> You really anticipate it every changing?
> Ever having machines that can't address bytes?
> I know they used to exist, but it has been several decades.
> The world's vast swaths of C, C++, Java, C# won't port easily to them.
> If I understood you, you argued that it is clearly IByte, so I should
> feel free to make up my own constants outside of TInt.i3/TWord.i3.
> Though so far I haven't.
>  
>  - Jay
> 
>  
> > From: hosking at cs.purdue.edu
> > Date: Wed, 10 Feb 2010 10:25:31 -0500
> > To: jkrell at elego.de
> > CC: m3commit at elegosoft.com
> > Subject: Re: [M3commit] CVS Update: cm3
> > 
> > On 10 Feb 2010, at 16:13, Jay Krell wrote:
> > 
> > > CVSROOT: /usr/cvs
> > > Changes by: jkrell at birch. 10/02/10 16:13:30
> > > 
> > > Modified files:
> > > cm3/m3-sys/m3middle/src/: TWord.m3 
> > > 
> > > Log message:
> > > just cleanup a little: make Mask and Base clear and not obfuscated, don't do the same compare twice in a row in xEQ (which should be plain EQ when I'm confident in its correctness, currently what EQ does is compute like three values and verify they all match)
> > 
> > Mask and Base are computed like that so it is easy to change the underlying representation of Target.Int. We might not have IByte, but instead have IWord!
> > 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3commit/attachments/20100210/3eb4e299/attachment-0002.html>