[M3devel] ROOT

[Tony Hosking]

On 2 Jul 2009, at 14:48, Jay wrote:

> Hopefully my other mail will help clear this up.

Jay, it's generally best to confine yourself to one e-mail instead of  
multiple.  My (mental) bandwidth is saturated by the number of e-mails  
I must read in a day, so I can't keep track of all of yours.

> I'd also like to do other Modula-3 work:
>    64 bit file sizes on all platforms
>     I'm at least going to try. This might cascade too far and break  
> a lot of things, since INTEGER and LONGINT cannot be freely  
> intermixed, you can't even assign an INTEGER to a LONGINT!

You can convert an INTEGER to a LONGINT.  It is deliberate that  
INTEGER and LONGINT be unrelated types, in keeping with the spirit of  
M3.  Implicit C casts are notorious sources of bugs.

>    Merge gcc-interix with gcc. It turns out this is quite small.
>
>   Enable the "portable runpaths" in Olaf's scripts (related to all  
> this).
>   I put the lines in slightly too far down in the code, oops.

Olaf, can you help clarify?

>
>
>
>  - Jay
>
> Date: Thu, 2 Jul 2009 14:31:45 -0400
> From: rcolebur at scires.com
> To: m3devel at elegosoft.com
> Subject: Re: [M3devel] ROOT
>
> I keep watching the various commit logs et al and I'm concerned too  
> that I don't readily understand what is going on and what the new  
> requirements will be going forward in terms of environment vars,  
> paths, and config file requirements, etc.
>
> As for ROOT, as an environment var, this is too generic.  If it is  
> required, it should be renamed to be specific, e.g. CM3_ROOT.
>
> Would it be possible to have a online conference about all this?
>
> Regards,
> Randy Coleburn

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