public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52101] Obsolescence warning for non-obs. feature character name*length
Date: Sun, 05 Feb 2012 18:12:00 -0000	[thread overview]
Message-ID: <bug-52101-4-MH4m0DaeNq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52101-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52101

--- Comment #9 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-02-05 18:11:41 UTC ---
(In reply to comment #8)
> > However, I have just check it and the font size seems to be the normal one.
> 
> It is sufficient once one reads B.2.8.

No, it isn't. B.1.8 gives a good hint, but not everything which is obsolescent
is in Appendix B. Additionally, Appendix B is only "informative". Thus, only
the font size of R504 matters, independent what nonnormative parts of the
standard claim.

However, we do not need to discuss this at length as of us agree that "entry-
name*len" is not obsolescent and only "character*len" is.


  parent reply	other threads:[~2012-02-05 18:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03  0:11 [Bug fortran/52101] New: " john.harper at vuw dot ac.nz
2012-02-03  7:22 ` [Bug fortran/52101] " burnus at gcc dot gnu.org
2012-02-03  7:31 ` burnus at gcc dot gnu.org
2012-02-03 20:51 ` John.Harper at msor dot vuw.ac.nz
2012-02-03 21:17 ` kargl at gcc dot gnu.org
2012-02-03 22:48 ` sgk at troutmask dot apl.washington.edu
2012-02-04  0:01 ` sgk at troutmask dot apl.washington.edu
2012-02-05  9:59 ` burnus at gcc dot gnu.org
2012-02-05 18:01 ` sgk at troutmask dot apl.washington.edu
2012-02-05 18:12 ` burnus at gcc dot gnu.org [this message]
2012-07-16 19:38 ` burnus at gcc dot gnu.org
2012-07-17  9:40 ` burnus at gcc dot gnu.org
2012-07-17 11:28 ` burnus 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-52101-4-MH4m0DaeNq@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).