[Info-vax] Roadmap

Bob Koehler koehler at eisner.nospam.decuserve.org
Tue Jan 8 09:59:25 EST 2019


In article <85022540-54d1-4a23-a7e5-517c5494e326 at googlegroups.com>, John Reagan <xyzzy1959 at gmail.com> writes:
> On Monday, January 7, 2019 at 2:06:29 PM UTC-5, Bob Koehler wrote:
>> In article <8e34e423-4b9d-4a1d-8b4e-0115c9d34319 at googlegroups.com>, gezelter at rlgsc.com writes:
>> > 
>> > However, in some cases, a program compiled with IEEE floating point may nee=
>> > d to access a binary file or a memory-resident data structure with a VAX fl=
>> > oating point representation. It is for this reason that I proposed adding t=
>> > he OpenVMS-specific optional qualifier.
>> > 
>> 
>>    Or write in Fortran, where the I/O subsystem will convert on the fly,
>>    even to/from formats only supported by hardware VMS never ran on.
> 
> I was avoiding mentioning this feature since it involves DFOR$ "feature logicals" :)

   I was under the impression that all of it could be accessed by using
   keywords in the OPEN statement.




More information about the Info-vax mailing list