From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 74159 invoked by alias); 26 Nov 2019 11:12:33 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 74139 invoked by uid 89); 26 Nov 2019 11:12:33 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-8.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=umbrella, csv, HContent-Transfer-Encoding:8bit X-HELO: esa2.mentor.iphmx.com Received: from esa2.mentor.iphmx.com (HELO esa2.mentor.iphmx.com) (68.232.141.98) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 26 Nov 2019 11:12:32 +0000 IronPort-SDR: zyDN56S16WQIHGa8GCs8saREtVsa+a0/K0rlNF3PIMKixtqAgi/T7uqr/jTdajdLb+XIza3UGx AYMGAZb77BtVPoFFcCLmyX81LypNwgt5Ljj8Pd95Y7kfmbT6evhZxIZKE0VIRZxDuO/qf3aNJW zFx0WFBsQLEV3h70D+9XiX814mraWttm6yWGjcXakni+EBB5+uvuqHJ+6iXvbW+4XQxHGPdNoG COTvOiyXRufWeiGpgqPK6/gq7TqVHKSOwV7nuVcq0FV5TTZQlpRYSNl20NEk+bmRozO2U6S6qE DmE= Received: from orw-gwy-01-in.mentorg.com ([192.94.38.165]) by esa2.mentor.iphmx.com with ESMTP; 26 Nov 2019 03:12:30 -0800 IronPort-SDR: OnCjinmksWBoNzWedUoN2STiLLmeIdYy+CZm/VaSxuhf2ckIu+ZfN0H6HJlyF7HRvvndxVOGbw VD+eFi4/0EovLqgScM9YOgwcJohS2QZG7FiAOmezo0bFcNpi0ICOOKykVyR/vykBIFgxkUPb+/ FpFEZTgu2kmSPSoHaaiiKBJ57EBK9jrBPw0WiEOcYh35bzMw9eKku/k9vk/IP5nQKDz98fmXjT m5pzZfUZPuoNZ5ielAnfGuuBFdIlVe3/2zLdle+dV3m5ssayASdX7+KCw37SuC4odG/TNqBM0U yGE= Subject: Re: [Patch, gcc-wwdocs] Update to Fortran changes To: Mark Eggleston , gcc-patches , fortran , References: <8de6eea3-ec83-dc45-0bfc-8c647e355a6f@codethink.co.uk> From: Tobias Burnus Message-ID: <02306a80-fb22-bbe9-9158-0033b65069e5@codesourcery.com> Date: Tue, 26 Nov 2019 11:33:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: <8de6eea3-ec83-dc45-0bfc-8c647e355a6f@codethink.co.uk> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit Return-Path: tobias@codesourcery.com X-IsSubscribed: yes X-SW-Source: 2019-11/txt/msg02395.txt.bz2 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"). > 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 (-fdec)" 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-…) In particular, currently, the following item does not make clear that it is about legacy support: "Variables with the AUTOMATIC attribute can be used in EQUIVALENCE statements." 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). Cheers, Tobias