[J3] Clarification on F18/017

[Daniel C Chen]

I think the main goal of this interp is to eliminate the double
finalization to the allocatable components that are also of finalizable
types.

However, the edits to fix this problem also introduce a "side-effect" that
the order of the finalization of such components are changed.

7.5.6.2 specifies only CBAP or CABP is valid output based on the current
standard, but the edits also allows CBPA.
I see and agree the argument that the parent component is just another
component and should be no different from other components.
However, as the current standard stands, 7.5.6.2 clearly intentionally put
the parent component to be the last to get finalized,
There are code that depends on that behaviour.
People who depend on that behaviour could also argue that components that
are allocatable or not should not change the existing rules that the parent
component should be finalized the last.

I have difficult time to find enough justification to fix the double
finalization issue by changing the order. On the other hand, I also
acknowledge that the edits actually relax the rules rather than make them
more restrictive.

Thanks,


Daniel

XL Fortran Development, Fortran Standard Representative
IBM Toronto Software Lab
Phone: 905-413-3056
Tie: 969-3056
Email: cdchen at ca.ibm.com
http://www.ibm.com/software/awdtools/fortran/xlfortran



From:	Steve Lionel via J3 <j3 at mailman.j3-fortran.org>
To:	j3 at mailman.j3-fortran.org
Cc:	Steve Lionel <steve at stevelionel.com>
Date:	2020-06-10 01:25 PM
Subject:	Re: [J3] [EXTERNAL] Re: Clarification on F18/017
Sent by:	"J3" <j3-bounces at mailman.j3-fortran.org>



On 6/10/2020 12:51 PM, Jibben, Zach via J3 wrote:
>
> Steve suggested:
>
> > how would you change the interp to satisfy the other requirements?
>
> Neil, Ondrej, and I worked out a set of edits which would satisfy the
> CBAP/CABP restriction. They definitely need more experienced eyes, but
> this is the idea:
>
Thanks, Zach (and others). I will now leave it to the more experienced
eyes to analyze this.

Steve



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20200610/e51be927/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20200610/e51be927/attachment-0001.gif>