[M3devel] the meaning of -FIRST(INTEGER)?

[Tony Hosking]

Agreed.  If we allow overflow at run-time we should at compile-time.

Antony Hosking | Associate Professor | Computer Science | Purdue University
305 N. University Street | West Lafayette | IN 47907 | USA
Office +1 765 494 6001 | Mobile +1 765 427 5484




On 23 Jan 2010, at 17:13, hendrik at topoi.pooq.com wrote:

> On Sat, Jan 23, 2010 at 07:30:33PM +0000, Jay K wrote:
>> 
>> Once I fix Lex.m3, should we continue to allow -FIRST(INTEGER) or not?
>> 
>> As well, should we go the extra bit and disallow it even if it doesn't overflow?
>>  ie: on one's complement?
> 
> The only reason for disallowing it is overflow, and then only for an 
> implementation that checks overflow.  But if it doesn't overflow, 
> it doesn't overflow, and it's valid.
> 
> -- hendrik
> 
>> I already disallow it in some code -- depending on which code gets
>> 
>> hit in the backend. But this disallowing is new.
> 
> It might warrant a portability warning, if we issue such.
> 
> -- hendrik

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100124/001d7332/attachment-0002.html>