public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46405] Preprocessor generated code can exceed 132 characters
Date: Thu, 16 Dec 2010 00:14:00 -0000 [thread overview]
Message-ID: <bug-46405-4-13R28B15an@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46405-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46405
Daniel Franke <dfranke at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dfranke at gcc dot gnu.org
--- Comment #5 from Daniel Franke <dfranke at gcc dot gnu.org> 2010-12-16 00:14:01 UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > I was thinking this same solution. But, maybe the user who is having the
> > problem should just do that.
>
> I think that's the cleanest solution. After all, even if the line length is
> only exceeded due to the CPP macro, it is still invaid Fortran.
Same here. Close as INVALID/WONTFIX?
next prev parent reply other threads:[~2010-12-16 0:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 1:30 [Bug fortran/46405] New: " w6ws at earthlink dot net
2010-11-10 9:06 ` [Bug fortran/46405] " burnus at gcc dot gnu.org
2010-11-14 13:39 ` tkoenig at gcc dot gnu.org
2010-11-14 19:10 ` jvdelisle at gcc dot gnu.org
2010-11-14 21:12 ` burnus at gcc dot gnu.org
2010-12-16 0:14 ` dfranke at gcc dot gnu.org [this message]
2010-12-27 0:28 ` dfranke at gcc dot gnu.org
2011-01-08 23:16 ` tkoenig at gcc dot gnu.org
2011-01-08 23:35 ` tkoenig at gcc dot gnu.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-46405-4-13R28B15an@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: 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).