Re: %LOC and %VAL availability
- From: Tobias Burnus <burnus@xxxxxxxx>
- Date: Wed, 25 Nov 2009 00:33:09 +0100
On Nov 24, 10:30 am, James Tursa <aclassyguywithakno...@xxxxxxxxxxx>
The non-standard %LOC() and %VAL() constructs are available in the
Intel Fortran and Compaq Fortran compilers that I have (32-bit,
WinXP). Are these constructs available in other compilers such as
gfortran, f95, etc? What about linux, mac, etc.? If not, is there a
workaround for this functionality? I am writing a package for others
to use and would like it to run in other environments out of the box
if possible. Thanks.
See the gfortran documentation for information concerning its
implementation of these constructs.
Short: gfortran supports %LOC(), %VAL() and %REF(), see
GCC/gfortran runs on a large variety of systems (Sparc, x86, arm, mips,
PowerPC, ia64, x86-64, s390, ...) and operating systems (FreeBSD, Linux,
Windows, Darwin (Mac), AIX, Solaris, HPUX, ...). [And the Intel compiler
you mention also runs on (x86 and x86-64) Windows, Linux and Mac.] Note,
however, that those are only supported as arguments in procedure calls
and not on their own (cf. "LOC()"). Note further that these all are
vendor extensions, which are relatively common but by far not supported
by all compilers.
As others have pointed out before, using the C binding support is the
better alternative. See, e.g.,
for an introduction, which should be relatively vendor agnostic.
The C binding support - as defined in the Fortran 2003 standard - is
present is a number of recent compilers, but older ones do not have it.
It depends on your users whether it is more likely that they have
compilers with %LOC, %VAL or with C binding support. But if you have the
choice, I would go for the latter. Advantages: (a) C bindings are well
defined (Fortran standard; vendor extensions tend to differ slightly
between vendors and even different versions). (b) I think the syntax is
also easier: You define what the procedure wants to get (e.g. a
pass-by-value argument) and then you simply pass the variable in the
call without having to care whether it should be a %VAL or a %REF or
%LOC. (c) The market share of older compilers is decreasing thus C
binding support should become more and more common.
Example for compilers not supporting %VAL: NAG f95. Example for not
supporting C bindings: Open64, g77. Examples for supporting both: ifort,
gfortran, sunf95, g95.
- Prev by Date: Re: %LOC and %VAL availability
- Next by Date: Re: Reading CSV files with missing data at the end
- Previous by thread: Re: %LOC and %VAL availability
- Next by thread: Re: %LOC and %VAL availability