This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [gfortran,patch] Add ISO_FORTRAN_ENV module

From: FX Coudert <fxcoudert at gmail dot com>
To: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
Cc: Fortran List <fortran at gcc dot gnu dot org>, gcc-patches patches <gcc-patches at gcc dot gnu dot org>
Date: Sun, 19 Nov 2006 21:55:59 +0100
Subject: Re: [gfortran,patch] Add ISO_FORTRAN_ENV module
References: <2C875733-99E1-4E44-BAC6-701E7E9C7325@gmail.com> <20061119204530.GA80545@troutmask.apl.washington.edu>

One other item.  Do you need to use uppercase names for
the symbols (e.g., "IOSTAT_END" instead of "iostat_end")?
I know that gfortran translates lowercase to upper as it
parses a file.  I tried tracing through the code to see
when/if uppercase is needed.

No, I think gfortran translates uppercase to lowercase when parsing the file, hence my choice for lowercase symbol names. We also use lowercase names, e.g., for intrinsic procedures.

I'll commit the patch soon with Tobias' and Brooks' changes.

Thanks everyone,
FX

References:
- [gfortran,patch] Add ISO_FORTRAN_ENV module
  - From: FX Coudert
- Re: [gfortran,patch] Add ISO_FORTRAN_ENV module
  - From: Steve Kargl

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]