Re: %LOC and %VAL availability

[glen herrmannsfeldt]

In a discussion on %LOC and %VAL in comp.lang.fortran, which
it seems were supposed to be generally available on VAX systems,
it occured to me that the % would conflict with the PL/I preprocessor.

Did VAX and/or VMS PL/I implementations avoid that problem?

-- glen

[Tim E. Sneddon]

PL/I on OpenVMS VAX and Alpha provides the DESCRIPTOR(), VALUE()
and REFERENCE().

As far as %LOC, PL/I already has the built-in ADDR() function to
achieve the same result.

Tim.

[robin]

"glen herrmannsfeldt" <g...@ugcs.caltech.edu> wrote in message news:hel2r6$gd7$2...@naig.caltech.edu...

As already explained to you in comp.lang.fortran,
%LOC etc were non-standard FORTRAN-specific.

PL/I didn't need those constructs, as it already
had its own suite of builtins and other mechanisms for that purpose.

[robin]

"glen herrmannsfeldt" <g...@ugcs.caltech.edu> wrote in message news:hel2n9$gd7$1...@naig.caltech.edu...
| Ken Fairfield <ken.fa...@gmail.com> wrote:
| (snip)
|
| > Glen, I surprised you would try to make such a distinction
| > between VAX and VMS. They were, after all, developed together,
| > one for the other, so to speak.
|
| OK, it is in "VAX11/780 Architecture Handbook", copyright 1977.
|
| Appendix C, "Procedure Calling and Condition Handling"
|
| The description of the calling convention says "VAX-11" thoughout.
| For Condition Handling it says VAX/VMS. It looks to me like someone
| wanted the calling convention to be OS independent, but realized
| that condition handling was VMS dependent.
|
| Though the % prefix will conflict with the PL/I preprocessor
| if one tries to do it for PL/I.

That has nothing to do with the price of fish.
In any case, PL/I has ADDR etc builtins.