[J3] (SC22WG5.6223) J3 Fortran interp letter ballot #36
Van Snyder
van.snyder at jpl.nasa.gov
Wed Jun 3 13:35:49 EDT 2020
The following Fortran interpretations are being balloted:
Yes No Number Title
-C- --- F18/015 Example in C.6.8 is wrong
I opposed the no-host-association semantics for interface bodies in
1986. My reasoning was that the prohibition makes it impossible to
write an interface body for a dummy procedure that has a derived-type
argument if the type is defined in the same scoping unit. It didn't
make sense to me. I still don't understand what purpose it served. I
don't remember the precise details of the discussion, and the Computer
History Museum now has my correspondence with X3J3 from that time so I
can't look it up.
-Y- --- F18/016 Host association changes in Fortran 2018
-Y- --- F18/017 Final subroutine invocation order
-C- --- F18/018 Public namelist and private variable
I disagree with A1: C8105 should exist. PRIVATE prevents access by use
association, of an identifier. The NAMELIST statement does not provide
access to any other scoping unit of a group object name. The name
remains private. But as A1 remarks, whether C8105 continues to exist is
an issue for a future standard.
More information about the J3
mailing list