[M3devel] Explicit types.

[Tony Hosking]

Hi Chris,

I think we gave settled on a good fit for long integer types for Modula-3.  Things are unlikely to change further.

--  Tony

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 18 Jan 2010, at 17:11, Chris wrote:

> I've spent some time perusing the source tree, and particularly anything dealing with 32/64 bit portability.
> 
> I'm wondering if it might make sense to define some explicit 32bit and 64bit types, perhaps at the library level, to ease porting. Types such as ...
> 	
> 	TYPE UnsignedInt64 ...
> 	TYPE SignedInt64 ...
> 	TYPE UnsignedInt32 ...
> 	TYPE SignedInt32 ...
> 
> etc...
> 
> Eventually the goal, as I understand it, is to have a 64bit LongInt type, however the above might serve useful as an intermediate step. The primary advantage to this approach is that the developers would know exactly what the machine representation of the variable/value is. No guesswork involved.
> 
> Also, as a step to full 64bit compatibility, it might make sense to define some sort of Region/Arena based memory manager that could be used in lieu of, or as an alternative to, the runtime garbage collector. Not as flexible, but far more predictable.
> 
> I'm doing some hacking on the tests, and I might try this approach with my local sources just to see how well(or poorly) it would work.
> 
> I'm still wrapping my brain around Modula 3s reference types, Thier slightly different from what I'm used to.
> 
> -- 
> Chris <Highjinks at gmx.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100118/646b47c4/attachment-0002.html>