public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/36058] Not allowing pointers to derived types in COMMON
Date: Tue, 29 Apr 2008 05:22:00 -0000	[thread overview]
Message-ID: <20080429052132.17933.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36058-15045@http.gcc.gnu.org/bugzilla/>



------- 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 way,

I don't really see how. I strongly agree with Tobias here. I think you
are confusing an important aspect of Fortran pointers with C ones. In
Fortran, pointer is an attribute. It does *NOT* make a separate type. If
the common-block-object has (derived) type x, then adding the pointer
attribute doesn't change the type. It is still of the same type and thus
the above restriction still applies.

If you try to read such words any other way, I think you'll find that
large parts of the standard fall apart - at least if one tries to apply
the same reading throughout the standard.
------------------------------


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36058


      parent reply	other threads:[~2008-04-29  5:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27  4:25 [Bug fortran/36058] New: " w6ws at earthlink dot net
2008-04-27  8:01 ` [Bug fortran/36058] " burnus at gcc dot gnu dot org
2008-04-27 13:24 ` w6ws at earthlink dot net
2008-04-27 15:31 ` burnus at gcc dot gnu dot org
2008-04-29  5:22 ` burnus at gcc dot gnu dot org [this message]

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=20080429052132.17933.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).