[Info-vax] Process memory settings

[Howard S Shubs]

In article <Vaidnbv6A5j01BjXnZ2dnUVZ_tWdnZ2d at earthlink.com>,
 "John Reagan" <johnrreagan at earthlink.net> wrote:

> "Howard S Shubs" <howard at shubs.net> wrote in message 
> news:howard-5D24CA.01314714082009 at news.newsguy.com...

> > When are y'all planning to make the 64-bit change, then?  Never?  I
> > tried to use 64-bit memory a week ago in C, and it was all good, until I
> > needed the Fortran I/O library, at which point Strange Things happened.
> > They stopped happening when I went back to 32-bit pointers.
> 
> That's a totally different question.  I'm talking about the compilers 
> themselves being 32-bit applications.

I see it as close since invoking a RTL for a particular language broke 
things using 64-bit code.


> User programs compiled BY those 32-bit compilers can certainly use 64-bit 
> pointers if the language supports it.  You should be able to use 64-bit 
> pointers in C, C++, Fortran, Macro-32, Pascal, and COBOL (for as much as 
> COBOL supports ANY pointer).

Agreed, I should be able to.


> If you had an F90 program that used 64-bit pointers but got strange results, 
> then somethings broken (either in your code, the F90 compiler, or the F90 
> RTL).  Read the Fortran release notes to see if you bumped into some known 
> restriction.

C code called by a Fortran program into which I added a bit of Fortran 
I/O, actually.

-- 
Don't bother with piddly crap like "gun control".
Life is 100% fatal.  Ban it.