From: Thomas Koenig <tkoenig@netcologne.de>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR37336 finalization
Date: Sat, 3 Jun 2023 07:50:19 +0200 [thread overview]
Message-ID: <552d5ed3-d137-b9dd-7b67-e561070aa001@netcologne.de> (raw)
In-Reply-To: <CAGkQGi+fY1wXokhdvf2bbfP9g3FOrY3j62xqvtheQL3HOzo85A@mail.gmail.com>
Hi Paul,
> I propose to backport
> r13-6747-gd7caf313525a46f200d7f5db1ba893f853774aee to 12-branch very
> soon.
Is this something that we usually do?
While finalization was basically broken before, some people still used
working subsets (or subsets that were broken, and they adapted or
wrote their code accordingly).
What is the general opinion on that? I'm undecided.
> Before that, I propose to remove the F2003/2008 finalization of
> structure and array constructors in 13- and 14-branches. I can see why
> it was removed from the standard in a correction to F2008 and think
> that it is likely to cause endless confusion and maintenance
> complications. However, finalization of function results within
> constructors will be retained.
That, I agree with. Should it be noted somewhere as an intentional
deviation from the standard?
Best regards
Thomas
next prev parent reply other threads:[~2023-06-03 5:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 13:45 Paul Richard Thomas
2023-03-07 14:58 ` Thomas Koenig
2023-03-07 17:15 ` Steve Kargl
2023-06-02 13:42 ` Paul Richard Thomas
2023-06-03 5:50 ` Thomas Koenig [this message]
2023-06-03 7:32 ` Steve Kargl
2023-06-03 13:16 ` Paul Richard Thomas
2023-06-03 19:10 ` Harald Anlauf
2023-06-03 19:10 ` Harald Anlauf
2023-06-03 19:22 ` Thomas Koenig
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=552d5ed3-d137-b9dd-7b67-e561070aa001@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
/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).