[J3] List of passed papers with approved edits

Malcolm Cohen malcolm at nag-j.co.jp
Mon Jul 20 20:39:22 EDT 2020


Hi Robert,

 

Thank you for the suggestion. I will consider making this editorial change when I get to 19-144.

 

Cheers,

-- 

..............Malcolm Cohen, NAG Oxford/Tokyo.

 

From: J3 <j3-bounces at mailman.j3-fortran.org> On Behalf Of Robert Corbett via J3
Sent: Sunday, July 19, 2020 5:09 PM
To: Malcolm Cohen via J3 <j3 at mailman.j3-fortran.org>
Cc: Robert Corbett <rpcorbett at att.net>
Subject: Re: [J3] List of passed papers with approved edits

 

I recommend against using the edit in paper

19-144 in the 202x standard.  That edit was

intended to be as small as possible for the

interp.  A better edit is possible for the

202x standard.

 

The definition of a procedure pointer in

18-0007r1 is

 

3.108.2

procedure pointer

procedure with the EXTERNAL and POINTER

attributes

 

A better definition is

 

procedure with the POINTER attribute

 

Any procedure with the POINTER attribute

is a procedure pointer.  Any procedure

does not have the POINTER attribute is not

a procedure pointer.  The EXTERNAL

attribute adds nothing.  The presence or

absence of the EXTERNAL attribute does

affect which procedures can or cannot be

given the POINTER attribute.

 

I can write an edit paper for this change.

The change is small, though it is larger

than the edit in 19-144.

 

Robert Corbett

 

On Saturday, July 18, 2020, 10:46:53 PM PDT, Malcolm Cohen via J3 <j3 at mailman.j3-fortran.org <mailto:j3 at mailman.j3-fortran.org> > wrote: 

 

 

Hi folks,

 

Below is my list of papers with approved edits either for approved features or editorial. I went through all the papers back to meeting 218 (before that I believe we were still in F2018 mode).

 

If anyone thinks there is anything wrong with this list (a missing paper, or a paper is included that should not be, or I have not listed the most recent revision, or there is a paper before meeting 218 which needs to be applied), please let me know asap. Otherwise the wrongness will be included in the next 007 draft where it could be a lot harder to spot!

 

(If you don’t see anything wrong, no need to comment as I am proceeding on the assumption that having checked everything twice, it’s probably okay.)

 

Paper action list

-----------------

 

1. Editorial

 

m218:

18-267 "Syntax errors in example codes"

19-115 "Making note of Statement Entities"

19-117 "Coarrays of type TEAM_TYPE"

19-143 "remaining block data subprogram"

19-144 "procedure pointer components"

19-162r1 "C_PTRDIFF_T"

 

m219:

19-165r1 "State that RECURSIVE has no semantics"

19-183r3 "Clarification of global identifier"

19-205 "Tweak wording in 19.4"

 

m220:

19-220r1 "Editorial fix to the description of REDUCE intrinsic"

19-233r1 "Minor editorial glitches"

 

m221:

20-100 "Editorial fix to Example for GET_ENVIRONMENT_VARIABLE intrinsic"

20-102r2 "FORM TEAM and failed images"

20-104r3 "Collective subroutines and STAT="

20-119 "Missing list items in 19.6.6"

20-123 "Edits for procedure pointer association"

 

2. Featural

 

m218:

19-137r2 "Specifications and Edits of AT" [this is US10]

19-138r1 "Specification and Edits for longer statements" [this is US01/US02]

19-139r1 "Specifications and Edits for log<n> & friends" [this is US06/US07/US08]

19-147r1 "SELECTED_LOGICAL_KIND" [this is US06/US07/US08]

19-149r1 "Require reports of ignorance" [this is US01/US02,]

19-156r1 "Control of leading zero in formatted numeric output" [this is US11]

 

m219:

XXXX Superseded 19-194r1 "C_F_POINTER modification for feature UK-01" do 19-238r1 instead.

19-195 "longer lines missing edit US01"

19-197r3 "Edits for C_F_STRPOINTER and F_C_STRING (US09)"

19-203r1 "Degree trigonometric functions (US04)"

19-204r1 "IEEE Circular trigonometric functions (US05)"

 

m220:

19-238r1 "C_F_POINTER modification for feature UK-01"

19-250r1 "US 12, arrays of coarrays"

19-254r2 "Edits for ISO_FORTRAN_STRINGS US03"

19-255r2 "Add reductions to DO CONCURRENT (US20)"

19-256r2, "US-23 Part 2, Standardizing use of BOZ constants"

19-259r1 "Edits for Put with Notify" [this is US13, and is missing from 20-010r1]

 

m221:

20-114r1 "Edits for TYPEOF and CLASSOF" [this is US16/17/18/24]

20-116r1 "Edits for SIMPLE procedures" [this is US15]

20-122r1 "Edits for US14 (auto-allocate characters)"

20-126r1 "Rank-agnostic allocation and pointer assignment Edits" [allegedly US16/17/18/24]

 

Cheers,

-- 

..............Malcolm Cohen, NAG Oxford/Tokyo.

 

 

Disclaimer

The Numerical Algorithms Group Ltd is a company registered in England and Wales with company number 1249803. The registered office is: Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom. Please see our Privacy Notice <https://www.nag.co.uk/content/privacy-notice>  for information on how we process personal data and for details of how to stop or limit communications from us.

This e-mail has been scanned for all viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20200721/89315cb1/attachment-0001.htm>


More information about the J3 mailing list