public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: fago@caltech.edu To: gcc-gnats@gcc.gnu.org Subject: preprocessor/5416: Need flag for cpp to allow fortran comments Date: Thu, 17 Jan 2002 11:36:00 -0000 [thread overview] Message-ID: <20020117193553.7953.qmail@sources.redhat.com> (raw) >Number: 5416 >Category: preprocessor >Synopsis: Need flag for cpp to allow fortran comments >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Thu Jan 17 11:36:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Matt Fago >Release: 3.0.2 >Organization: >Environment: System: Linux phlebas 2.4.17 #2 Fri Jan 11 13:00:38 PST 2002 i686 unknown Architecture: i686 >Description: CPP does not currently understand fortran-type comments. I understand the reasoning behind this (as cpp is primarily for C), but it can cause considerable inconvienence when cpp is used with fortran source. I have a very large project in Fortran (written elsewhere) that contains hundreds of unmatched quotes in the fortran comments. It is necessary (although not too difficult) to deal with these. It would be much nicer in the future if I could simply tell cpp to ignore the comments. >How-To-Repeat: process a fortran file with the line: C What's wrong with this comment? >Fix: Add a "-fortran-comments" type flag to cpp that instructs cpp to correctly deal with fortran style comments. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-01-17 19:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-17 11:36 fago [this message] 2002-01-17 13:54 neil 2002-01-17 18:46 Matt Fago 2002-01-17 23:36 Neil Booth
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=20020117193553.7953.qmail@sources.redhat.com \ --to=fago@caltech.edu \ --cc=gcc-gnats@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).