<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>[truncated again..]<BR><BR><BR><BR><BR>
<BLOCKQUOTE>
<HR id=EC_stopSpelling>
From: jayk123@hotmail.com<BR>To: hosking@cs.purdue.edu<BR>CC: m3devel@elegosoft.com<BR>Subject: RE: [M3devel] small set comparisons understood, now just to understand the front end code..<BR>Date: Mon, 14 Apr 2008 17:55:47 +0000<BR><BR>
<META content="Microsoft SafeHTML" name=Generator>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass body.EC_hmmessage
{font-size:10pt;font-family:Tahoma;}
</STYLE>
If they fit in an INT32, use an INT32.<BR>But if they fit in an INT64, that's still probably more efficient than an otherwise "big set".<BR> Well, of course, there's always the inline vs. non-inline size vs. speed.<BR>And here I teeter toward hypocricy in taking advantage of two "natural" integer types.<BR>Heck, generalize it to a list of efficient sizes: 8, 16, 32, 64, pick the smallest that fits, and in the future when otherwise there would have been LONGLONGINT, add 128 to the list.<BR> <BR> - Jay<BR><BR>[snip]</BLOCKQUOTE></body>
</html>