public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Matt Fago <fago@caltech.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: preprocessor/5416: Need flag for cpp to allow fortran comments
Date: Thu, 17 Jan 2002 18:46:00 -0000	[thread overview]
Message-ID: <20020118024602.20694.qmail@sources.redhat.com> (raw)

The following reply was made to PR preprocessor/5416; it has been noted by GNATS.

From: Matt Fago <fago@caltech.edu>
To: neil@gcc.gnu.org, fago@caltech.edu, gcc-bugs@gcc.gnu.org,
        gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: preprocessor/5416: Need flag for cpp to allow fortran comments
Date: Thu, 17 Jan 2002 18:37:52 -0800

 Using cpp with g77 is abusing cpp? I hope not!  I can certainly use sed, 
 but I had hoped it would not be necessary in the future. BTW, suggesting 
 that people use c-style comments in Fortran code seems silly, and would 
 be difficult in my case even with sed.
 
 As for nixing the change ... ok, I certainly don't know the details.
 
 Matt
 
 On Thursday, January 17, 2002, at 01:54  PM, neil@gcc.gnu.org wrote:
 
 > Synopsis: Need flag for cpp to allow fortran comments
 >
 > State-Changed-From-To: open->closed
 > State-Changed-By: neil
 > State-Changed-When: Thu Jan 17 13:54:26 2002
 > State-Changed-Why:
 >     I really have no interest in implementing this; we don't
 >     want to encourage people to abuse cpp.  I expect that most
 >     of your problems would be solved by -traditional with
 >     judicious use of a tool like sed.
 >
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
 > trail&database=gcc&pr=5416
 >
 


             reply	other threads:[~2002-01-18  2:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17 18:46 Matt Fago [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-17 23:36 Neil Booth
2002-01-17 13:54 neil
2002-01-17 11:36 fago

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=20020118024602.20694.qmail@sources.redhat.com \
    --to=fago@caltech.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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: link
Be 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).