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/32876] Wrongly accepts private items in public NAMELISTs Date: Wed, 25 Jul 2007 18:09:00 -0000 [thread overview] Message-ID: <20070725180935.7384.qmail@sourceware.org> (raw) In-Reply-To: <bug-32876-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from burnus at gcc dot gnu dot org 2007-07-25 18:09 ------- > I think that, by extension, components with private components must be illegal > too. Which means checking over several levels. For the following program, g95 gives an error. (NAG f95, ifort don't.) > I'll have a look. Thanks, Daniel. module x type tp3 private integer :: i end type tp3 type tp2 type(tp3) :: t end type tp2 type tp1 integer :: i type(tp2) :: t end type tp1 type(tp1) :: t1 integer :: j namelist /a/ t1,j end module x -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32876
next prev parent reply other threads:[~2007-07-25 18:09 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-24 13:43 [Bug fortran/32876] New: " burnus at gcc dot gnu dot org 2007-07-25 5:13 ` [Bug fortran/32876] " pault at gcc dot gnu dot org 2007-07-25 17:57 ` dfranke at gcc dot gnu dot org 2007-07-25 18:09 ` burnus at gcc dot gnu dot org [this message] 2007-07-28 8:51 ` dfranke at gcc dot gnu dot org 2007-07-28 8:54 ` dfranke at gcc dot gnu dot org
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=20070725180935.7384.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: linkBe 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).