This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/36325] specific or generic INTERFACE implies the EXTERNAL attribute
- From: "burnus at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 25 May 2008 17:11:48 -0000
- Subject: [Bug fortran/36325] specific or generic INTERFACE implies the EXTERNAL attribute
- References: <bug-36325-14773@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from burnus at gcc dot gnu dot org 2008-05-25 17:11 -------
> Which leads me to think we should probably implement this (for the case that
> the interface is explicit). Or is there any good reason that this is not done?
Well, regarding the reason: Before interfaces had no EXTERNAL attribute and
those procedures with EXTERNAL attribute had no explicit interface.
That interfaces have the EXTERNAL attribute only needed for procedure pointers.
One could think of not giving the EXTERNAL attribute to procedures declared in
interface bodies and modifying POINTER / the pointer resolution only. I'm not
sure what is cleaner and simpler.
Regarding our questions, Richard Maine (mostly) answered them. See URL in
comment #3.
conf2(external,dimension)
is in any case wrong. It should be:
conflict(external with implicit interface, dimension)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36325