public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "toon at moene dot indiv dot nluug dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/35203] New: OPTIONAL, VALUE actual argument cannot be an INTEGER 0 Date: Thu, 14 Feb 2008 23:05:00 -0000 [thread overview] Message-ID: <bug-35203-109@http.gcc.gnu.org/bugzilla/> (raw) Run this program: INTERFACE SUBROUTINE AAP(I) INTEGER, OPTIONAL, VALUE :: I END SUBROUTINE END INTERFACE CALL AAP(0) END SUBROUTINE AAP(N) INTEGER, OPTIONAL, VALUE :: N IF (PRESENT(N)) THEN PRINT*,'PRESENT, WITH VALUE:',N ELSE PRINT*,'NOT PRESENT' ENDIF END and get: $ ./a.out NOT PRESENT $ which should come to no surprise, if one glazes his/her eyes over trans_expr.c:gfc_conv_missing_dummy. -- Summary: OPTIONAL, VALUE actual argument cannot be an INTEGER 0 Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: toon at moene dot indiv dot nluug dot nl http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35203
next reply other threads:[~2008-02-14 23:05 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-14 23:05 toon at moene dot indiv dot nluug dot nl [this message] 2008-02-14 23:47 ` [Bug fortran/35203] " burnus at gcc dot gnu dot org 2008-02-15 0:03 ` burnus at gcc dot gnu dot org 2008-02-15 1:04 ` toon at moene dot indiv dot nluug dot nl 2008-02-15 1:07 ` toon at moene dot indiv dot nluug dot nl 2008-02-15 6:12 ` jvdelisle at gcc dot gnu dot org 2008-02-15 6:36 ` jvdelisle at gcc dot gnu dot org 2008-02-15 7:18 ` burnus at gcc dot gnu dot org 2008-02-15 18:15 ` toon at moene dot indiv dot nluug dot nl 2008-02-15 20:05 ` burnus at gcc dot gnu dot org 2008-02-18 8:32 ` toon at moene dot indiv dot nluug dot nl 2008-03-26 21:10 ` tobi 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=bug-35203-109@http.gcc.gnu.org/bugzilla/ \ --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).