Re: preprocessor/5416: Need flag for cpp to allow fortran comments

Re: preprocessor/5416: Need flag for cpp to allow fortran comments

[Matt Fago]

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
 >
 

Re: preprocessor/5416: Need flag for cpp to allow fortran comments

[Neil Booth]

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

From: Neil Booth <neil@daikokuya.demon.co.uk>
To: Matt Fago <fago@caltech.edu>
Cc: neil@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: preprocessor/5416: Need flag for cpp to allow fortran comments
Date: Fri, 18 Jan 2002 07:28:49 +0000

 Matt Fago wrote:-
 
 > Using cpp with g77 is abusing cpp? I hope not!
 
 Of course it is, Fortran is not C, or a C-family language.
 
 > 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.
 
 I didn't suggest using C-style comments.
 
 Neil.

Re: preprocessor/5416: Need flag for cpp to allow fortran comments

[neil]

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

preprocessor/5416: Need flag for cpp to allow fortran comments

[fago]

>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: