[M3commit] tint

[Tony Hosking]

I'm not sure what you mean.  The initializers in TInt.i3 *are* correct  
for any 2s-complement representation of one byte or more.  Thus, if  
someone was to change the representation as defined in Target they  
would *not* need changing in TInt.i3.  ".." is perfectly well-defined  
syntax to indicate continue with (in this case) the high-order bits  
exactly as they are ...

Antony Hosking | Associate Professor | Computer Science | Purdue  
University
305 N. University Street | West Lafayette | IN 47907 | USA
Office +1 765 494 6001 | Mobile +1 765 427 5484



On Mar 2, 2008, at 9:16 PM, Jay wrote:

> Tony, it is definitely confusing to claim the array has NUMBER(x)  
> elements, and then initialize only some of them "correctly".
> Trailing zeros I can see as maybe clear for positive values, but  
> definitely confusing for negative values.
>
>  - Jay
>
>
> > Date: Mon, 3 Mar 2008 01:26:48 +0000
> > To: m3commit at elegosoft.com
> > From: hosking at elego.de
> > Subject: [M3commit] CVS Update: cm3
> >
> > CVSROOT:	/usr/cvs
> > Changes by:	hosking at birch.	08/03/03 01:26:48
> >
> > Modified files:
> > cm3/m3-sys/m3middle/src/: TInt.i3
> >
> > Log message:
> > Not sure what Jay objected to here! It is perfectly concise as is  
> and more
> > obvious than what he put in.
> >
>
> Climb to the top of the charts! Play the word scramble challenge  
> with star power. Play now!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3commit/attachments/20080302/5b64aad8/attachment-0002.html>