[M3devel] FW: small set comparisons understood, now just to understand the front end code..

[Jay]

[truncated again..]


From: jayk123 at hotmail.comTo: hosking at cs.purdue.eduCC: m3devel at elegosoft.comSubject: RE: [M3devel] small set comparisons understood, now just to understand the front end code..Date: Mon, 14 Apr 2008 17:55:47 +0000


If they fit in an INT32, use an INT32.But if they fit in an INT64, that's still probably more efficient than an otherwise "big set".   Well, of course, there's always the inline vs. non-inline size vs. speed.And here I teeter toward hypocricy in taking advantage of two "natural" integer types.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.  - Jay[snip]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20080414/ac244a05/attachment-0002.html>