public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tobi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/19101] missing & in character continuation not caught Date: Mon, 27 Dec 2004 21:47:00 -0000 [thread overview] Message-ID: <20041227214706.27710.qmail@sourceware.org> (raw) In-Reply-To: <20041221094200.19101.Thomas.Koenig@online.de> ------- Additional Comments From tobi at gcc dot gnu dot org 2004-12-27 21:47 ------- Actually, my misleading reference is by the same authors the same as Erik's, it's the "Fortran 90 Handbook". Looks like they got it wrong. I think I have a fix, it wasn't too hard :-) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19101
next prev parent reply other threads:[~2004-12-27 21:47 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-21 9:42 [Bug fortran/19101] New: " Thomas dot Koenig at online dot de 2004-12-21 18:49 ` [Bug fortran/19101] " pinskia at gcc dot gnu dot org 2004-12-25 0:41 ` eedelman at acclab dot helsinki dot fi 2004-12-25 9:31 ` Thomas dot Koenig at online dot de 2004-12-27 21:41 ` tobi at gcc dot gnu dot org 2004-12-27 21:47 ` tobi at gcc dot gnu dot org [this message] 2004-12-28 19:19 ` tobi at gcc dot gnu dot org [not found] <bug-19101-9515@http.gcc.gnu.org/bugzilla/> 2006-02-22 2:01 ` jvdelisle at gcc dot gnu dot org 2006-03-06 6:23 ` jvdelisle at gcc dot gnu dot org 2006-03-08 7:35 ` patchapp at dberlin dot org 2006-03-09 6:08 ` jvdelisle at gcc dot gnu dot org 2006-03-12 5:15 ` patchapp at dberlin dot org 2006-03-15 7:03 ` jvdelisle at gcc dot gnu dot org 2006-03-15 7:08 ` jvdelisle at gcc dot gnu dot org 2006-04-07 21:08 ` jvdelisle at gcc dot gnu dot org 2006-04-07 21:12 ` jvdelisle at gcc dot gnu dot org 2006-04-07 21:20 ` jvdelisle 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=20041227214706.27710.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).