<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Rodney I *think* generally mixed sizes are supported in TWord, TInt.<BR>
Though I don't necessarily understand all of the code.<BR>
There was a problem recently fixed, granted.<BR>
One problem here though is that you can't TWord.Extract beyond the size.<BR>
So the varying sizes of "zero" behave differently.<BR>
You might imagine it's zeros as far out as needed, but it doesn't work that way currently.<BR>
<BR>
- Jay<BR> <BR>> Date: Mon, 8 Feb 2010 10:02:58 -0600<BR>> From: rodney_bates@lcwb.coop<BR>> To: m3commit@elegosoft.com<BR>> Subject: Re: [M3commit] CVS Update: cm3<BR>> <BR>> <BR>> <BR>> Jay K wrote:<BR>> > I wonder if we need<BR>> > TInt8, TInt16, TInt32, TInt64, TInt, TLong<BR>> > TWord8, TWord16, TWord32, TWord64, TWord, TLongWord<BR>> > <BR>> > that accurately implement ints/words of the exact specified size,<BR>> > with TInt/TWord/TLong/TLongWord depending on the target.<BR>> > I wouldn't mind trying to remove this word "Word".<BR>> > And replace it with UInt or such.<BR>> > TInt, TUInt, TLong, TULong?<BR>> > TSignedInt, TUnsignedInt, TSignedLong, TUnsignedLong?<BR>> > TInt, TUnsignedInt, TLong, TUnsignedLong?<BR>> > <BR>> > TInt.Zero is just always 8 bytes.<BR>> > The size is I believe meant to be fairly opaque to the user.<BR>> > This is the first I've noticed it being visible, such that TInt.EQ is <BR>> > true for values with "quite different" behavior. I would have "thunk" <BR>> > (thought without much thought) that anything TInt.EQ is more equivalent <BR>> > than they actually are.<BR>> > <BR>> <BR>> Hmm. I recall in a discussion a while back that the arithmetic on<BR>> target ints was not coded to handle operands with mixed values of<BR>> n. Could this have something to do with this?<BR>> <BR>> > <BR>> > - Jay<BR>> > <BR>> > <BR>> ><BR> </body>
</html>