Second attempt this time with attachment.
Apologies.
regards,
Mark
On 26/11/2019 15:56, Mark Eggleston wrote:
On 26/11/2019 11:12, Tobias Burnus wrote:
Hi Mark,
On 11/26/19 11:46 AM, Mark Eggleston wrote:
I've check the changes with W3 validator. There are no problems
related to my changes, however, it does object to the lack of
character encoding in the file.
Note that some script modifies the file a bit – the final file does
have a character encoding (content="text/html; charset=utf-8").
Understood.
This is the first time in changing the wwwdoc, I haven't included a
change log as there there doesn't appear to be any ChangeLog files.
There is only a commit log (see 'git log'); the format is still a bit
in a flux as before there was only 'csv' where it applied to a single
file.
[With git it is useful to have a meaningful single line (for "git log
--pretty=oneline") and, if needed, an empty line and something more.
As the main repository is going to move to GIT as well, this also
applies there. – But you already follow this style.]
The patch is attached. OK to commit?
I wonder whether you should use a main bullet point with something
like "Legacy improvements (<code>-fdec</code>)" under which you put
the current list. [Or some other wording.] That makes it easier to
read for users – those, who care about legacy support, can quickly
look at the -fdec changes – while those interested in standard
Fortran can skip it. (Except for the character-diagnostic type-info
improvement, all are items seem to be for -fdec or -fdec-…)
Used "Legacy extension:".
In particular, currently, the following item does not make clear that
it is about legacy support: "Variables with the
<code>AUTOMATIC</code> attribute can be used in
<code>EQUIVALENCE</code> statements."
Made it clear that this an extension of -fdec-static.
I think it can remain as is with the -fdec umbrella item. But without
it really requires the background knowledge that the AUTOMATIC
attribute is only available with -fdec-static (or -fdec).
Stated that -fdec-static or -fdec are needed to use AUTOMATIC in
EQUIVALENCE.
Cheers,
Tobias
Changes acceptable? OK to commit?
--
https://www.codethink.co.uk/privacy.html
>From f884924877ba84578e75bd16cb127bab33eb5ee6 Mon Sep 17 00:00:00 2001
From: Mark Eggleston <markeggles...@codethink.com>
Date: Tue, 26 Nov 2019 10:12:44 +0000
Subject: [PATCH] Update Fortran changes
---
htdocs/gcc-10/changes.html | 41 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 52eb303..a31e7e5 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -206,6 +206,47 @@ a work-in-progress.</p>
with <code>-std=legacy</code>. <code>-Wargument-mismatch</code>
has been removed.
</li>
+ <li>
+ Legacy extensions:
+ <ul>
+ <li>
+ Default fields widths can be used for <code>I</code>, <code>F</code>
+ and <code>G</code> format specifiers when excplicit widths are omitted.
+ Use the option <code>-fdec-format-defaults</code>, this options is implied
+ with <code>-fdec</code>.
+ </li>
+ <li>
+ A blank format item at the end of a format specification i.e. nothing
+ following the final comma is allowed. Use the option
+ <code>-fdec-blank-format-item</code>, this options is implied with
+ <code>-fdec</code>.
+ </li>
+ <li>
+ The existing support for <code>AUTOMATIC</code> and <code>STATIC</code>
+ attributes has been extended to allow variables with the
+ <code>AUTOMATIC</code> attribute to be used in <code>EQUIVALENCE</code>
+ statements. Use <code>-fdec-static</code>, this option is implied by
+ <code>-fdec</code>.
+ </li>
+ <li>
+ Allow character literals in assignments and <code>DATA</code> statements
+ for numeric (<code>INTEGER</code>, <code>REAL</code>, or
+ <code>COMPLEX</code>) or <code>LOGICAL</code> variables. Use the option
+ <code>-fdec-char-conversions</code>, this options is implied with
+ <code>-fdec</code>.
+ </li>
+ <li>
+ DEC comparisons, i.e. allow Hollerith constants to be used in comparisons
+ with <code>INTEGER</code>, <code>REAL</code>, <code>COMPLEX</code> and
+ <code>CHARACTER</code> expressions. Use the option <code>-fdec</code>.
+ </li>
+ </ul>
+ <li>
+ Character type names in errors and warnings now include <code>len</code>
+ in addition to <code>kind</code>, <code>*</code> is used for assumed
+ length. The kind is omitted if it the default kind. Examples:
+ <code>CHARACTER(12)</code>, <code>CHARACTER(6,4)</code>.
+ </li>
</ul>
<!-- <h3 id="go">Go</h3> -->
--
1.8.3.1