From: FX <fxcoudert@gmail.com>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] fortran/67802 -- Numeric constant character length must ...
Date: Thu, 01 Oct 2015 20:49:00 -0000 [thread overview]
Message-ID: <E7933F37-BDFC-4932-9D5A-177EF6D09251@gmail.com> (raw)
In-Reply-To: <20151001194521.GA7929@troutmask.apl.washington.edu>
> Well, ahem, gfortran does have several error messages that use the
> standard notation. I know. I wrote some of them. :-)
>
> I'll simply change it to "Expecting an INTEGER at %L”
Thanks. I have no objections to using the full standard terminology (scalar integer expression), but not the shorthand (scalar-int-expr) which few people outside the language lawyers know :)
FX
next prev parent reply other threads:[~2015-10-01 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 18:54 Steve Kargl
2015-10-01 19:19 ` FX
2015-10-01 19:45 ` Steve Kargl
2015-10-01 20:49 ` FX [this message]
2015-10-01 21:19 Dominique d'Humières
2015-10-01 23:25 ` Steve Kargl
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=E7933F37-BDFC-4932-9D5A-177EF6D09251@gmail.com \
--to=fxcoudert@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).