From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 117290 invoked by alias); 17 Sep 2018 21:37:01 -0000 Mailing-List: contact fortran-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: fortran-owner@gcc.gnu.org Received: (qmail 117268 invoked by uid 89); 17 Sep 2018 21:37:00 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=acuerdo, HTo:D*ar, estoy, greatly X-HELO: mail-yw1-f66.google.com Received: from mail-yw1-f66.google.com (HELO mail-yw1-f66.google.com) (209.85.161.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 17 Sep 2018 21:36:58 +0000 Received: by mail-yw1-f66.google.com with SMTP id x67-v6so6103232ywg.0 for ; Mon, 17 Sep 2018 14:36:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NbA/pP2MWtopqzUO9HASbASQPFoQBJl8nG064I3p9pg=; b=qSSY5zhAI/58P+f7CQ64iWsye7yZGAICaZlzWbUwhPnlII6PgcEW8Th6WbUguLm/gQ m324lenGv156AU5BctUXMbTNU/SywAdP7cuGAs+mxTy/OecaztjAKkNg/lKooxQ0YYBk DwpblTM0RgJREQnICGoXfFwU4UjgtpHon0I97N1nT6W1PzZ52NwrGu1tIOexuubCOVl4 MD+9Ipib0enk129KG/nYF/pZAuKQWUUn5v0HVRn6P9AHXZBhwS/KnM2ZuLe+JoPJGolx q6szY+qH/D6ET7gyDOVTIOsBu801v7l7r1c2M9O7k43hq/oLe6u2mzUf+MUXSm2grvCP fAjg== MIME-Version: 1.0 Received: by 2002:a81:7a4b:0:0:0:0:0 with HTTP; Mon, 17 Sep 2018 14:36:55 -0700 (PDT) In-Reply-To: <2146573646.16532.1537219646324.JavaMail.zimbra@intec.unl.edu.ar> References: <2146573646.16532.1537219646324.JavaMail.zimbra@intec.unl.edu.ar> From: Paul Richard Thomas Date: Mon, 17 Sep 2018 21:37:00 -0000 Message-ID: Subject: Re: Benefits of continuing Fortran standardisation survey: interim results To: "Jorge D'Elia" Cc: Gfortran List Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2018-09/txt/msg00116.txt.bz2 Dear Jorge, ....snip.... >> However, it is clear that the versions being used in the >> field are lagging far behind trunk. > > Perhaps encourage the users the convenience or need to update > the compiler version with a short phrase in the commands like > "gfortran --version", etc., as well as in the manual or on the > wiki page? The problem, reading between the lines is that many users are in the hands of system administrators, who do not greatly like straying outside the confines of the distro. ....snip.... > > Although the array descriptor ABIs are not compatible, some > compatibility in the * .mod files would be very welcome, at > least partially, and thus avoid introducing a lot of extra work. Unfortunately, I think that it would now take more work to make .mod files compatible than the ABI. > >> "Fortran is a dead language and its use should be banned by >> an act of Parliament." >> (Well, I suppose that it would make a change from brexit.) > > The anonymous opinion is somewhat unfriendly because it is > innecesary and it is a statement not technically justified. Which one - about fortran or brexit? :-) ....snip.... > In the case of the Gfortran manual, the "standard" label in each > intrinsic is very useful to quickly verify in what Fortran > standard (95, 2003, 2008, etc.) is available. You are correct. However, the commentator is correctly pointing out that the different brands have different bugs for the F20xx features. ....snip.... >> "gfortran - yes (although it would be nice if coarrays were better >> integrated, i.e. not having to use the opencoarray library >> explicitly)." >> (Music for your ears, Nicolas and Thomas!) > > I would also like a better integration of coarrays in case of > processing either with shared or distributed memory. Then, a > little more music for Nicolas and Thomas... Estoy de acuerdo! Paul