public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67250] gfortran does not faithfully preprocess the way cpp does
Date: Tue, 18 Aug 2015 06:28:00 -0000	[thread overview]
Message-ID: <bug-67250-4-7jhWvIRWnJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67250-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67250

--- Comment #11 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Aug 18, 2015 at 06:03:00AM +0000, jeff.science at gmail dot com wrote:
> 
> In short, "it's not in the standard, therefore it's fine to break user
> experience" seems pretty weak here.  It's fine if you tell me that you do not
> care about my needs and will not implement it, but please don't use ISO as the
> excuse.
> 

Well, no.  It's not standard, so a compiler implementation
is free define its own behavior.  The gfortran manual
has documented its behavior for a very long time.  Have
you read the gfortran manual?


  parent reply	other threads:[~2015-08-18  6:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17 15:59 [Bug fortran/67250] New: " jeff.science at gmail dot com
2015-08-17 16:19 ` [Bug fortran/67250] " pinskia at gcc dot gnu.org
2015-08-17 16:43 ` manu at gcc dot gnu.org
2015-08-17 20:01 ` pinskia at gcc dot gnu.org
2015-08-17 21:07 ` kargl at gcc dot gnu.org
2015-08-18  5:34 ` jeff.science at gmail dot com
2015-08-18  5:41 ` pinskia at gcc dot gnu.org
2015-08-18  6:03 ` jeff.science at gmail dot com
2015-08-18  6:13 ` pinskia at gcc dot gnu.org
2015-08-18  6:28 ` sgk at troutmask dot apl.washington.edu [this message]
2015-08-18 21:46 ` jeff.science at gmail dot com
2015-08-19 12:46 ` manu 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-67250-4-7jhWvIRWnJ@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).