It would also seem reasonable that *IF* the promotion checking requires any significant amount of resources that there be a non-promoting version/mode of the ops for calculations that are known a priori to not overflow (e.g. i = 0; i = i + 1; <=== Should be able to be designated *somehow* to not check for overflow)
-----Original Message----- From: Dan Sugalski [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 25, 2004 8:39 AM To: [EMAIL PROTECTED] Subject: Tight typing by default? It seems pretty clear that the general opinion is that operations should produce the tightest reasonable type for an operation--integer multiplication should produce an integer unless it can't, for example. For our purposes I think the typing should go: platform int->float->bignum with an operation producing a type no tighter than the loosest type in the operation. (so int/float gives a float, float-bignum gives a bignum) This seem reasonable? -- Dan --------------------------------------it's like this------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk The information contained in this e-mail message is privileged and/or confidential and is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by telephone (330-668-5000), and destroy the original message. Thank you.
