home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!elroy.jpl.nasa.gov!sdd.hp.com!caen!deccrl!news.crl.dec.com!rdg.dec.com!uvo.dec.com!e2big.mko.dec.com!quark.enet.dec.com!lionel
- From: lionel@quark.enet.dec.com (Steve Lionel)
- Subject: Re: Question on OpenVMS and VAX FORTRAN
- Message-ID: <1992Nov23.150412.12084@e2big.mko.dec.com>
- Keywords: Fortran, shareable images, MACRO, RTL
- Lines: 67
- Sender: usenet@e2big.mko.dec.com (Mr. USENET)
- Reply-To: lionel@quark.enet.dec.com (Steve Lionel)
- Organization: Digital Equipment Corporation, Nashua NH
- References: <1992Nov22.152400.14845@doug.cae.wisc.edu>
- Distribution: comp.lang.fortran
- Date: Mon, 23 Nov 1992 15:04:12 GMT
-
-
- In article <1992Nov22.152400.14845@doug.cae.wisc.edu>, dafnioti@cae.wisc.edu
- (Petros Dafniotis) writes:
- |>(*) will shareable images be available in OpenVMS right away the same way
- |> as in VAX/VMS
-
- Yes, shareable images are available, but they are actually easier to create
- on OpenVMS AXP as you don't need to code a transfer vector in MACRO. Please
- make sure you read the OpenVMS AXP linker documentation on this subject.
-
- |>(*) will OpenVMS fortran be 100% compatible (as language not binaries of
- |> course) with VAX fortran?
-
- As close as we could make it. Here is the list of language features we
- deliberately omitted from DEC Fortran for OpenVMS AXP:
-
- Radix-50 constants, the routines IRAD50, RAD50 and R50ASC
- PDP-11 compatibility routines ASSIGN, CLOSE, ERRSET, ERRTST,
- FDBSET and USEREX
- The REAL*16 datatype (but Q-exponent constants are accepted and
- treated as REAL*8)
-
- The default REAL*8 datatype on AXP is G_float, so if your program passes
- REAL*4 values to REAL*8 arguments or vice versa, you've got a latent bug.
- The D_float format is available on AXP but with the same precision as
- G_float (53 bits). IEEE floating is also available.
-
- VAX FORTRAN allows you to pass a character literal as an actual argument to
- a Fortran subroutine or function which receives it as non-character; DEC
- Fortran for OpenVMS AXP requires you to use %REF if you mismatch argument
- types in this manner.
-
- Lastly, DICTIONARY support is waiting for CDD/Repository availability. Any
- other omissions or differences in implementation are unintentional and we want
- to hear about them.
-
- |>(*) are all the wonderful SYS$,LIB$,SMG$ etc routines of system and RTL be
- |> in openVMS totally compatible with the VAX/VMS?
-
- Pretty much all except for those which are VAX architecture specific, such as
- LIB$DECODE_FAULT, etc. There are some new routines, and at least one old
- one (LIB$TPARSE) has a new equivalent that requires recoding to use. If you
- depend on "precise arithmetic exceptions", some rework will likely be needed.
-
- |>(*) in conclusion: can someone give me some information regarding what will
- |> be different in OpenVMS wrt VAX/VMS (other than binaries and possibly
- |> fundamental types eg. longwords etc)?
-
- As little as we could manage. Some of the more advanced VAX/VMS features
- won't be available in the early releases of OpenVMS AXP, but those will fill
- in over time.
-
- |>(*) can someone point me to a source (ftp,journal,book) where i can learn
- |> more about alpha and OpenVMS?
-
- See a previous posting about quick FAX information about AXP, or your
- Digital representative. I'll also be glad to answer specific questions about
- Fortran.
-
- --
-
- Steve Lionel lionel@quark.enet.dec.com
- DEC Fortran/VAX FORTRAN Development
- SDT Languages Group
- Digital Equipment Corporation
- 110 Spit Brook Road
- Nashua, NH 03062
-