--- Comment #4 from burnus at gcc dot gnu dot org 2008-04-29 05:21 ---
Close as INVALID.
Richard Maine wrote in c.l.f (see link above):
--
> > Contrary to you, my reading is that this applies also to a pointer to
> > a derived type.
>
> I can read it either w
--- Comment #3 from burnus at gcc dot gnu dot org 2008-04-27 15:30 ---
See also:
http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/773de8d5b57f8e20
(In reply to comment #2)
> I am only concerned with the POINTER case. I am not placing a
> derived type object in the
--- Comment #2 from w6ws at earthlink dot net 2008-04-27 13:24 ---
Subject: Re: Not allowing pointers to derived types in
COMMON
burnus at gcc dot gnu dot org wrote:
> --- Comment #1 from burnus at gcc dot gnu dot org 2008-04-27 08:01
> ---
> gfortran's rejection is in line
--- Comment #1 from burnus at gcc dot gnu dot org 2008-04-27 08:01 ---
gfortran's rejection is in line with g95, NAG f95, ifort, openf95, sunf95 and
ifort.
I think gfortran is right and the sequence (or bind(C)) attribute is needed.
The reason is the same as for the following program:
