This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/46405] Preprocessor generated code can exceed 132 characters
- From: "burnus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 14 Nov 2010 19:17:48 +0000
- Subject: [Bug fortran/46405] Preprocessor generated code can exceed 132 characters
- Auto-submitted: auto-generated
- References: <bug-46405-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46405
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2010-11-14 19:16:10 UTC ---
(In reply to comment #2)
> We _could_ set the line length to unlimited when invoking the preprocessor
> automagically.
> Would this be a good idea? Hmm...
I do not think that that's the proper solution. In that case you do not
distinguish between lines which are genuine too long and those which are only
too long due to the macro processing. I think if you want to have the latter,
you need to plug into libcpp and add a line-length check there.
Then, you can as a second step disable the line length check in the front-end
itself.
(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.
> Is there a flag we can check and
> just not truncate at 132 or whatever length if CPP?
Well, there is gfc_cpp_enabled().