public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Jerry DeLisle via Fortran <fortran@gcc.gnu.org>
Subject: Re: Error on left hand function reference
Date: Wed, 11 Jan 2023 19:07:26 -0800	[thread overview]
Message-ID: <Y795bpMLR7Wa5sJw@troutmask.apl.washington.edu> (raw)
In-Reply-To: <9fcade0f-a67e-35ba-e6d0-dc0f90b18d39@protonmail.com>

On Thu, Jan 12, 2023 at 02:31:12AM +0000, Jerry DeLisle via Fortran wrote:
> Hi all,
> 
> I spotted this today on the Fortran-Lang Discourse.
> 
> It would not be setting precednce for us to allow an extension and turn
> this into a warning with -std=gnu and an error of strict compliance is
> wanted.
> 
> https://fortran-lang.discourse.group/t/error-the-leftmost-part-ref-in-a-data-ref-cannot-be-a-function-reference/4990
> 
> I will create a PR and chase this one if concurrence here.
> 
> Opinions?
> 

gfortran's current behavior is standard conforming.  Personally,
I think this should not be implemented in gfortran.  If you do
scratch the itch, then please hide it behind some option such as
-fallow-nonconforming-Fortran-leftmost-part-reference-function-component.
Please, do not enable it under -std=gnu (which should be deprecated
in favor of -std=f2018 and then -std=f2023).  Putting it under -std=gnu
would imply that it will be supported in future versions of gfortran
and would need to support whatever is implemented now and whatever
might get standardized in the future.

I'll send end by noting that there are several unimplemented F2018
features and F2023 will be approved in the April-ish timeframe.

-- 
Steve

      reply	other threads:[~2023-01-12  3:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12  2:31 Jerry DeLisle
2023-01-12  3:07 ` Steve Kargl [this message]

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=Y795bpMLR7Wa5sJw@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=fortran@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).