October 2020 WG5/J3 meeting

[certik]

Zach and I will use this issue to keep the community updated on the work of the WG5 and J3 Committees at the October 2020 (virtual) meeting.

The documents for this meeting are here.

Monday 10/12/2020

JoR:

• 20-140: Passed with unanimous consent. This paper modifies examples for auto-allocating arguments to intrinsic procedures.
• 20-141: As amended, passed with unanimous consent.
• 20-139: Passed with unanimous consent. This paper changes the API for the new intrinsic for splitting strings. (Spec & syntax: 19-245r1)
• 20-137: As amended, passed with unanimous consent. This paper adds edits clarifying backwards-compatibility-breaking changes on auto-reallocating strings in write statements.

Data:

• 20-142: Passed, 11 for 2 against. May be backed out later if there is no syntax with strong support.

HPC:

• 20-145: Passed with unanimous consent.
• 20-146: Passed with unanimous consent.

Tuesday (10/13/2020)

Generics:

• 20-148: Discussed, to be revised and voted tomorrow.
• 20-135: passed unanimously, as amended.
• 20-144: withdrawn, resubmit tomorrow (associated discussion at #157)

JoR:

• 20-155: preliminary vote, rework for tomorrow.
• 20-158r2: passed with unanimous consent.
• 20-160: withdrawn, will resubmit tomorrow
• 20-153r1: passed with unanimous consent

Wednesday (10/14/2020)

Interp:

• 20-138r1: As amended, passed with unanimous consent.
• 20-149: As amended, passed with unanimous consent.
• 20-152r1: Passed with unanimous consent, with the alternative edit.

Edit:

• 20-133r2: As amended, passed with unanimous consent.

HPC:

• 20-156: As amended, passed with unanimous consent.
• 20-162: Withdrawn for revision.
• 20-163: Passed with unanimous consent.

Generics:

• 20-148r1: As amended, passed with unanimous consent.
• 20-144r1: As amended, passed with 10 for and 3 against.

JoR:

• 20-160r2: As amended, passed with unanimous consent.
• 20-155r1: Withdrawn.

Data:

• 20-131: Passed with unanimous consent.

[tclune]

I agree that the situation is a bit inconsistent in a fairly trivial sense, but there are arguments for how things turned out.

Related aspects that I find amusing:

(1) The true “original sin” on this front is the explicit TYPE() used to designate derived types back in F90. (And begrudgingly now allow for intrinsics). Were it not for that, I would have spelled TYPEOF(x) as TYPE(x). The parens are read out loud as “of”.

(2) Oddly it does not take much to make such redundant declarations acceptable. Somehow KIND=KIND(x) is more acceptable than RANK(RANK(x)) even though though there are punctuation marks in exactly the same places save for an extra trailing paren (which I very much doubt is the problem).

Cheers,

• Tom

On Oct 23, 2020, at 7:31 AM, Bill Long notifications@github.com<mailto:notifications@github.com> wrote:

On Oct 22, 2020, at 10:45 PM, William B. Clodius notifications@github.com<mailto:notifications@github.com> wrote:

Maybe what would be useful are RANKOF and SHAPEOF specifiers similar in spirit to the TYPEOF and CLASSOF specifiers of 202X.

There are already proposals for RANK and BOUNDS attributes. RANK confusingly has the same spelling as the RANK intrinsic, so instead of RANKOF(X) we now have RANK(RANK(X)), I think your proposed spellings are better.

Cheers, BIll

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Bill Long longb@hpe.commailto:longb@hpe.com Engineer/Master , Fortran Technical Support & voice: 651-605-9024 Bioinformatics Software Development fax: 651-605-9143 Hewlett Packard Enterprise/ 2131 Lindau Lane/ Suite 1000/ Bloomington, MN 55425

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_j3-2Dfortran_fortran-5Fproposals_issues_185-23issuecomment-2D715285479&d=DwMFaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=EDCdNzkccJ25Co3sjWrr1HlJQ3_CoIFWfekFE1ulcLI&m=NCv5fRaKxFoLClpI1Gefn4jnfP0YmLlghmVp3Ly9ypU&s=ogxpI0aIUrHNMDHdM5uF4Ii5ERZ-K7BIvsrPDYsSOwE&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ABPP7YCLTOQYVCHKJOIUB7TSMFSPVANCNFSM4SNKWX4Q&d=DwMFaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=EDCdNzkccJ25Co3sjWrr1HlJQ3_CoIFWfekFE1ulcLI&m=NCv5fRaKxFoLClpI1Gefn4jnfP0YmLlghmVp3Ly9ypU&s=bdVvenvu7R-TNKa49saPtREw4unGN_n6ObqygONO0zs&e=.