public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/25217] Derived type dummy argument having intent(out) attribute
Date: Sun, 09 Jul 2006 07:48:00 -0000	[thread overview]
Message-ID: <20060709074841.5310.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25217-11798@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from steven at gcc dot gnu dot org  2006-07-09 07:48 -------
To quote from the F95 June 97 working draft, note 12.17:

"Because an INTENT(OUT) variable is considered undefined on entry to the
procedure, any default initialization specified for its type will be applied."

Of the fortran bugs we have, this is one of the more serious bugs.


-- 

steven at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2005-12-02 19:28:17         |2006-07-09 07:48:40
               date|                            |


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


  parent reply	other threads:[~2006-07-09  7:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02  4:17 [Bug fortran/25217] New: " sudeshc at noida dot hcltech dot com
2005-12-02 19:28 ` [Bug fortran/25217] " eedelman at gcc dot gnu dot org
2006-07-09  7:48 ` steven at gcc dot gnu dot org [this message]
2006-07-18 18:28 ` eedelman at gcc dot gnu dot org
2006-07-18 20:40 ` patchapp at dberlin dot org
2006-08-19 21:06 ` eedelman at gcc dot gnu dot org
2006-08-19 21:32 ` eedelman at gcc dot gnu dot org
2006-08-20  0:46 ` steven at gcc dot gnu dot org
2006-08-20 16:25 ` eedelman 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=20060709074841.5310.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).