public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "godom at twinbee dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/37032] New: Multi-line comments in an included file trigger invalid character Date: Tue, 05 Aug 2008 18:52:00 -0000 [thread overview] Message-ID: <bug-37032-16565@http.gcc.gnu.org/bugzilla/> (raw) Multi-line comments in an included file trigger "invalid character in name" compiler error. !file1.F95 program file1 include 'file2.F95' stop end program !file2.F95 /* blah */ -- Summary: Multi-line comments in an included file trigger invalid character Product: gcc Version: 4.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: godom at twinbee dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37032
next reply other threads:[~2008-08-05 18:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-05 18:52 godom at twinbee dot com [this message] 2008-08-05 19:23 ` [Bug fortran/37032] including "file.F90" - no CPP processing burnus at gcc dot gnu dot org 2008-08-05 21:09 ` godom at twinbee dot com 2008-08-05 21:19 ` kargl at gcc dot gnu dot org 2008-08-05 21:31 ` godom at twinbee dot com 2008-08-05 21:45 ` kargl at gcc dot gnu dot org 2008-08-05 22:06 ` godom at twinbee dot com 2008-08-06 6:14 ` burnus at gcc dot gnu dot org 2008-08-14 21:18 ` dfranke at gcc dot gnu dot org 2008-08-18 20:48 ` dfranke at gcc dot gnu dot org 2008-08-18 20:52 ` 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=bug-37032-16565@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).