From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR33541 - gfortran wrongly imports renamed-use-associated symbol unrenamed
Date: Thu, 22 Nov 2007 23:15:00 -0000 [thread overview]
Message-ID: <4745DD4D.7090804@moene.indiv.nluug.nl> (raw)
In-Reply-To: <339c37f20711220744k1ff8096ar2221a1467bf2b626@mail.gmail.com>
Paul Richard Thomas wrote:
> I find this part of the standard to be quite obscure
> and much prefer the description of the DEC Fortran manual:
>
> << If more than one USE statement for a given module appears in a
> scoping unit, the following rules apply:
>
> If one USE statement does not have the ONLY option, all public
> entities in the module are accessible, and any rename- lists and
> only-lists are interpreted as a single, concatenated rename-list.
>
> If all the USE statements have ONLY options, all the only-lists are
> interpreted as a single, concatenated only-list. Only those entities
> named in one or more of the only-lists are accessible. >>
Well, then perhaps we (J3) should add that (or something similar) as a note.
Kind regards,
--
Toon Moene - e-mail: toon@moene.indiv.nluug.nl - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
At home: http://moene.indiv.nluug.nl/~toon/
GNU Fortran's path to Fortran 2003: http://gcc.gnu.org/wiki/Fortran2003
next prev parent reply other threads:[~2007-11-22 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 19:49 Paul Richard Thomas
2007-11-22 20:54 ` Paul Richard Thomas
2007-11-22 21:16 ` Paul Richard Thomas
2007-11-23 23:56 ` Paul Richard Thomas
2007-11-24 4:58 ` Jerry DeLisle
2007-11-22 23:15 ` Toon Moene [this message]
2007-11-26 0:56 ` Paul Richard Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4745DD4D.7090804@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).