public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paulthomas2 at wanadoo dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/18879] ? not supported in namelist input Date: Sun, 13 Mar 2005 17:59:00 -0000 [thread overview] Message-ID: <20050313175947.21354.qmail@sourceware.org> (raw) In-Reply-To: <20041207213320.18879.Thomas.Koenig@online.de> ------- Additional Comments From paulthomas2 at wanadoo dot fr 2005-03-13 17:59 ------- (In reply to comment #2) This is indeed and extension. See http://h18009.www1.hp.com/fortran/docs/lrm/lrm0372.htm#nm_in for the Digital/Compaq/HP specification > (In reply to comment #1) > > Is this a language extension? Seems likely, as the standard has no concept of > > stdin and stdout. Could you point to someplace where this extension is specified? > It's in the comments to io.h (line 76 ff): > Even more complex, during the execution of a program containing a > namelist READ statement, you can specify a question mark character(?) > or a question mark character preceded by an equal sign(=?) to get > the information of the namelist group. By '?', the name of variables > in the namelist will be displayed, by '=?', the name and value of > Also, check out http://h18009.www1.hp.com/fortran/docs/lrm/lrm0372.htm . > It's specified in green, which I suppose means that it is an extension. > Googling for "namelist fortran question mark" will lead to other > examples. > Offhand, I can't find a UNIX compiler that doesn't support it. g77 also > tries, but the support there is buggy (see PR 18874). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18879
next prev parent reply other threads:[~2005-03-13 17:59 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-07 21:33 [Bug libfortran/18879] New: " Thomas dot Koenig at online dot de 2004-12-08 14:48 ` [Bug libfortran/18879] " tobi at gcc dot gnu dot org 2004-12-08 16:24 ` Thomas dot Koenig at online dot de 2004-12-10 11:00 ` Thomas dot Koenig at online dot de 2005-01-06 14:42 ` tobi at gcc dot gnu dot org 2005-03-13 17:59 ` paulthomas2 at wanadoo dot fr [this message] 2005-04-18 7:54 ` [Bug libfortran/18879] [4.0 only] " fxcoudert at gcc dot gnu dot org 2005-04-18 14:41 ` pinskia at gcc dot gnu dot org 2005-06-05 23:35 ` cvs-commit at gcc dot gnu dot org 2005-07-01 22:11 ` pinskia at gcc dot gnu dot org 2005-07-01 22:11 ` pinskia 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=20050313175947.21354.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).