[M3devel] still need a branch for longint changes?

[Jay K]

I'm fine with a compromise that requires no runtime checks and users use ORD() to narrow LONGINT to INTEGER.

And mixed arithmetic is available, and assignability INTEGER to LONGINT.

I have that implemented. It is a little onerous for Rd/Wr uses, but ok.

 

 - Jay

 


From: hosking at cs.purdue.edu
Date: Fri, 8 Jan 2010 21:23:15 -0500
To: jay.krell at cornell.edu
CC: m3devel at elegosoft.com
Subject: Re: [M3devel] still need a branch for longint changes?


Please hold off on mainline changes.  I don't think we have reached consensus yet...


The issue remains: mixed arithmetic + checked assignability or not?  I'm leaning towards allowing it, but want to hear from others.



On 8 Jan 2010, at 21:16, Jay K wrote:

Still need a branch for longint changes?
 I doubt what I have is where we are going, though it is a step toward it.
 Just wait for Tony to implement Rodney's proposal?
 Or I work on it in a branch? It doesn't look too difficult to at least mostly do. I already have "mixed" stuff compiling and assignability INTEGER to LONGINT. I didn't yet do anything requiring runtime checks, but it's not that hard to do, given that there are already checks for assignment involving only partly overlapping ranges.

Or maybe just take my stuff to the mainline and then refine/reduce it later?

 - Jay


 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100109/0d2b4846/attachment-0002.html>