[M3commit] CVS Update: cm3

[Rodney M. Bates]

Jay K wrote:
> I wonder if we need
>   TInt8, TInt16, TInt32, TInt64, TInt, TLong
>   TWord8, TWord16, TWord32, TWord64, TWord, TLongWord
>  
> that accurately implement ints/words of the exact specified size,
> with TInt/TWord/TLong/TLongWord depending on the target.
> I wouldn't mind trying to remove this word "Word".
> And replace it with UInt or such.
> TInt, TUInt, TLong, TULong?
> TSignedInt, TUnsignedInt, TSignedLong, TUnsignedLong?
> TInt, TUnsignedInt, TLong, TUnsignedLong?
>  
> TInt.Zero is just always 8 bytes.
> The size is I believe meant to be fairly opaque to the user.
> This is the first I've noticed it being visible, such that TInt.EQ is 
> true for values with "quite different" behavior. I would have "thunk" 
> (thought without much thought) that anything TInt.EQ is more equivalent 
> than they actually are.
>  

Hmm.  I recall in a discussion a while back that the arithmetic on
target ints was not coded to handle operands with mixed values of
n.  Could this have something to do with this?

>  
>  - Jay
> 
>  
>