From steve at stevelionel.com  Thu Jun  1 14:42:31 2023
From: steve at stevelionel.com (Steve Lionel)
Date: Thu, 1 Jun 2023 10:42:31 -0400
Subject: [J3] [SC22WG5.6444] Manchester meeting, FDIS, WG5 web site
Message-ID: <20230601144239.0CA2D3591A3@www.open-std.org>

Hello all,

We're just over a week away from the Manchester WG5/J3 meeting and I 
look forward to seeing many of you in person again. For those attending 
by Zoom, Plenary connection details are at Meeting #230 (June 12-16, 
2023) Zoom Connection Info - J3 Work Items (j3-fortran.org) 
<https://j3-fortran.org/forum/viewtopic.php?f=3&t=128>? For those of you 
new to this, you log in to the discussion board with the same 
credentials as you use at j3-fortran.org. If you are a J3/WG5 member and 
don't have a site login, please send me mail directly 
<mailto:steve at stevelionel.com> (do not reply to the list.) Subgroup 
connection details will be posted in that thread when available. Please 
do not post Zoom connection details to the email lists.

The current status of the FDIS is that the ISO editor rejected it, 
citing some of the same complaints as she did for the DIS. Malcolm, Bill 
Ash and I will be meeting with her next week to discuss this, and it is 
my hope that we can agree to make some smaller changes and leave major 
issues such as typeface and font size to the next revision, as it would 
take months to rework the document (we discussed this at M229.)

As ISO has removed public access from "General Information" documents, 
including many I linked from wg5-fortran.org, the site now has local 
copies of those documents and the links have been changed to reference 
them. This is an ongoing issue between SC22 and JTC1 - despite promises 
for public access years ago, it has not materialized.

Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230601/f4edc536/attachment.htm>

From Nathan.Sircombe at arm.com  Mon Jun  5 11:31:41 2023
From: Nathan.Sircombe at arm.com (Nathan Sircombe)
Date: Mon, 5 Jun 2023 11:31:41 +0000
Subject: [J3] Local arrangements for WG5 in Manchester, 12 - 16 June.
In-Reply-To: <PA4PR08MB7409DC360B079ABED33E25CBF7409@PA4PR08MB7409.eurprd08.prod.outlook.com>
References: <PA4PR08MB7409E0C34EFFE8131FAF50FDF7899@PA4PR08MB7409.eurprd08.prod.outlook.com>
 <PA4PR08MB740962CD0AA4A4F96A719CFAF7769@PA4PR08MB7409.eurprd08.prod.outlook.com>
 <PA4PR08MB7409E98D597E244DD5BF1ADFF7759@PA4PR08MB7409.eurprd08.prod.outlook.com>
 <PA4PR08MB7409DC360B079ABED33E25CBF7409@PA4PR08MB7409.eurprd08.prod.outlook.com>
Message-ID: <PA4PR08MB7409CB708072BA380FBC1381F74DA@PA4PR08MB7409.eurprd08.prod.outlook.com>

Hi,

A quick request for those attending in-person.

There will (as is the custom?) be some catering for the meeting (snacks on Tues-Thursday, hopefully a lunch on the Wednesday) .

So if you have any allergies or dietary requirements (and you?ve not sent them to me already) please could you let me know ASAP.

Cheers,
Nathan.


From: J3 <j3-bounces at mailman.j3-fortran.org> on behalf of Nathan Sircombe via J3 <j3 at mailman.j3-fortran.org>
Date: Tuesday, 23 May 2023 at 5:08 pm
To: General J3 interest list <j3 at mailman.j3-fortran.org>, sc22wg5 at open-std.org <sc22wg5 at open-std.org>
Cc: Nathan Sircombe <Nathan.Sircombe at arm.com>
Subject: Re: [J3] Local arrangements for WG5 in Manchester, 12 - 16 June.
Hi,

If you?re attending the meeting in Manchester in person and are interested in any of the social activities below, please let me know.

Cheers,
Nathan.

From: Nathan Sircombe <Nathan.Sircombe at arm.com>
Date: Friday, 12 May 2023 at 5:07 pm
To: General J3 interest list <j3 at mailman.j3-fortran.org>, sc22wg5 at open-std.org <sc22wg5 at open-std.org>
Subject: Local arrangements for WG5 in Manchester, 12 - 16 June.
Hello everybody,

The next WG5 meeting, in Manchester UK, is just a month away!
The block reservation deadline for room reservations at the nearby Ibis Styles expires in a couple of days, so if you intend to take advantage of this, please make your booking asap if you?ve not already. Hotel details can be found at the end of this message.

Don?t forget to register for the meeting on the ISO website here: https://sd.iso.org/meetings/126106

I have made a paper with some details of the local arrangements, which is available here: https://wg5-fortran.org/N2201-N2250/N2214.txt

Something that is conspicuously absent from those arrangements is Social Activities! I?d like to get an idea of numbers, and any specific requirements. Provisionally I was thinking?


  *   Sunday afternoon: for those who?ve made it to the City by this point, I thought it might be good to meet up and take a look round Manchester?s Museum of Science and Industry (MoSI) - https://www.scienceandindustrymuseum.org.uk. It?s free to enter, although the ?Power Up? exhibit, for anyone craving some games console nostalgia  - https://www.scienceandindustrymuseum.org.uk/whats-on/power-up ? is paid entry.
After that, we could go for food. There?s a wide variety in Manchester, but my default suggestion would be the Italian restaurant Salvi?s, not far from MoSI - https://salvismanchester.co.uk/restaurants/salvis-deansgate-square/
  *   Thursday evening: a social event, all details TBC ? but I?m looking at Society - https://www.societymanchester.com.

If you would like to attend either / both of these, please email me directly and let me know by the end of next week (2012-05-19), so I can start to firm-up arrangements.
Also, please indicate if anyone will be accompanying you, and if you?ve got any specific dietary requirements.

Cheers,
Nathan.


The hotel details again are?
Ibis Styles
96 Portland Street,
Manchester
M1 4GX.
Map: https://w3w.co/venue.mats.waving

Rooms available from 2023-06-11:
Single occupancy
@ ?129 per night
bed & breakfast
Double occupancy
@ ?139 per night
bed & breakfast
Booking:
Email Danielle Fairhurst, the Reservations & Conferences Manager at HA0H5-RE at accor.com<mailto:HA0H5-RE at accor.com>
State that it?s for the ?Arm Manchester, WG5 meeting?.
Danielle will provide details on how to secure the reservation.

The rooms will be held until 28 days to go (2023-05-14). Cancellations after this point will be non-refundable.

Please note: The Parklife festival is taking place in the city from June 10-11, this impacts room availability for the Saturday before the meeting. I recommend you plan to arrive in the city on the Sunday if possible.

If you're considering staying elsewhere and would like some advice, please get in touch.


IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230605/863cd9f1/attachment-0001.htm>

From Nathan.Sircombe at arm.com  Mon Jun  5 11:31:41 2023
From: Nathan.Sircombe at arm.com (Nathan Sircombe)
Date: Mon, 5 Jun 2023 11:31:41 +0000
Subject: [J3] [SC22WG5.6445] Local arrangements for WG5 in Manchester,
 12 - 16 June.
In-Reply-To: <PA4PR08MB7409DC360B079ABED33E25CBF7409@PA4PR08MB7409.eurprd08.prod.outlook.com>
References: <PA4PR08MB7409E0C34EFFE8131FAF50FDF7899@PA4PR08MB7409.eurprd08.prod.outlook.com>
 <PA4PR08MB740962CD0AA4A4F96A719CFAF7769@PA4PR08MB7409.eurprd08.prod.outlook.com>
 <PA4PR08MB7409E98D597E244DD5BF1ADFF7759@PA4PR08MB7409.eurprd08.prod.outlook.com>
 <PA4PR08MB7409DC360B079ABED33E25CBF7409@PA4PR08MB7409.eurprd08.prod.outlook.com>
Message-ID: <PA4PR08MB7409CB708072BA380FBC1381F74DA@PA4PR08MB7409.eurprd08.prod.outlook.com>

Hi,

A quick request for those attending in-person.

There will (as is the custom?) be some catering for the meeting (snacks on Tues-Thursday, hopefully a lunch on the Wednesday) .

So if you have any allergies or dietary requirements (and you?ve not sent them to me already) please could you let me know ASAP.

Cheers,
Nathan.


From: J3 <j3-bounces at mailman.j3-fortran.org> on behalf of Nathan Sircombe via J3 <j3 at mailman.j3-fortran.org>
Date: Tuesday, 23 May 2023 at 5:08 pm
To: General J3 interest list <j3 at mailman.j3-fortran.org>, sc22wg5 at open-std.org <sc22wg5 at open-std.org>
Cc: Nathan Sircombe <Nathan.Sircombe at arm.com>
Subject: Re: [J3] Local arrangements for WG5 in Manchester, 12 - 16 June.
Hi,

If you?re attending the meeting in Manchester in person and are interested in any of the social activities below, please let me know.

Cheers,
Nathan.

From: Nathan Sircombe <Nathan.Sircombe at arm.com>
Date: Friday, 12 May 2023 at 5:07 pm
To: General J3 interest list <j3 at mailman.j3-fortran.org>, sc22wg5 at open-std.org <sc22wg5 at open-std.org>
Subject: Local arrangements for WG5 in Manchester, 12 - 16 June.
Hello everybody,

The next WG5 meeting, in Manchester UK, is just a month away!
The block reservation deadline for room reservations at the nearby Ibis Styles expires in a couple of days, so if you intend to take advantage of this, please make your booking asap if you?ve not already. Hotel details can be found at the end of this message.

Don?t forget to register for the meeting on the ISO website here: https://sd.iso.org/meetings/126106

I have made a paper with some details of the local arrangements, which is available here: https://wg5-fortran.org/N2201-N2250/N2214.txt

Something that is conspicuously absent from those arrangements is Social Activities! I?d like to get an idea of numbers, and any specific requirements. Provisionally I was thinking?


  *   Sunday afternoon: for those who?ve made it to the City by this point, I thought it might be good to meet up and take a look round Manchester?s Museum of Science and Industry (MoSI) - https://www.scienceandindustrymuseum.org.uk. It?s free to enter, although the ?Power Up? exhibit, for anyone craving some games console nostalgia  - https://www.scienceandindustrymuseum.org.uk/whats-on/power-up ? is paid entry.
After that, we could go for food. There?s a wide variety in Manchester, but my default suggestion would be the Italian restaurant Salvi?s, not far from MoSI - https://salvismanchester.co.uk/restaurants/salvis-deansgate-square/
  *   Thursday evening: a social event, all details TBC ? but I?m looking at Society - https://www.societymanchester.com.

If you would like to attend either / both of these, please email me directly and let me know by the end of next week (2012-05-19), so I can start to firm-up arrangements.
Also, please indicate if anyone will be accompanying you, and if you?ve got any specific dietary requirements.

Cheers,
Nathan.


The hotel details again are?
Ibis Styles
96 Portland Street,
Manchester
M1 4GX.
Map: https://w3w.co/venue.mats.waving

Rooms available from 2023-06-11:
Single occupancy
@ ?129 per night
bed & breakfast
Double occupancy
@ ?139 per night
bed & breakfast
Booking:
Email Danielle Fairhurst, the Reservations & Conferences Manager at HA0H5-RE at accor.com<mailto:HA0H5-RE at accor.com>
State that it?s for the ?Arm Manchester, WG5 meeting?.
Danielle will provide details on how to secure the reservation.

The rooms will be held until 28 days to go (2023-05-14). Cancellations after this point will be non-refundable.

Please note: The Parklife festival is taking place in the city from June 10-11, this impacts room availability for the Saturday before the meeting. I recommend you plan to arrive in the city on the Sunday if possible.

If you're considering staying elsewhere and would like some advice, please get in touch.


IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230605/863cd9f1/attachment-0003.htm>

From steve at stevelionel.com  Thu Jun  8 00:08:04 2023
From: steve at stevelionel.com (Steve Lionel)
Date: Wed, 7 Jun 2023 20:08:04 -0400
Subject: [J3] [SC22WG5.6447] WG23 resolution
Message-ID: <20230608000807.8ACAE3591CE@www.open-std.org>

Hello all,

Those of you who have been with us for a while will know that there's 
been an ongoing project to create a "Fortran annex" to a WG23 document 
relating to programming language vulnerabilities. Dan Nagle championed 
this for many years, and since then, several of us, including John Reid, 
Tom Clune and myself, along with others, have been working with WG23 
Convenor Stephen Michell to finish this. We're essentially done, with 
just some formatting and minor issues to complete.

WG23 is requesting that WG5 approve the latest draft, which I have 
uploaded as https://wg5-fortran.org/ARCHIVE/WG23-N1301-20230605.pdf , as 
"essentially complete" and to give permission to WG23 to complete the 
document and submit it for ballot as an international standard. I would 
like this to be one of the resolutions for the Manchester meeting.

Please let me know if you have questions.

Steve


From danlnagle at mac.com  Thu Jun  8 21:18:21 2023
From: danlnagle at mac.com (Dan Nagle)
Date: Thu, 8 Jun 2023 15:18:21 -0600
Subject: [J3] [SC22WG5.6447] WG23 resolution
In-Reply-To: <20230608000807.8ACAE3591CE@www.open-std.org>
References: <20230608000807.8ACAE3591CE@www.open-std.org>
Message-ID: <592C3835-F065-4E77-AE35-C8B24E3EC9B4@mac.com>

Hi,

I have read the draft WG23 N1301.

Kudos to those who persevered to completion.
My apologies for not carrying the ball further,
but now the goal line is realistically in reach.

A couple of comments, of course!

In 6.2.2 and other places, the out_of_range() intrinsic is not mentioned.
I would have thought it's worthy of a good brag.

In 6.3.2, left-most is mentioned, but not right-most.  I couldn't deduce
a reason from the surrounding text.

In 6.6.1, iostat is always >0 for errors, no?  The <0 values are "informative"
as end-of-record or end-of-file or similar.

If my observations are not reproducible, please ignore them.

My sincere congratulations to those who finished the job, and did so so well.  :-)




> On Jun 7, 2023, at 18:08, Steve Lionel via J3 <j3 at mailman.j3-fortran.org> wrote:
> 
> Hello all,
> 
> Those of you who have been with us for a while will know that there's been an ongoing project to create a "Fortran annex" to a WG23 document relating to programming language vulnerabilities. Dan Nagle championed this for many years, and since then, several of us, including John Reid, Tom Clune and myself, along with others, have been working with WG23 Convenor Stephen Michell to finish this. We're essentially done, with just some formatting and minor issues to complete.
> 
> WG23 is requesting that WG5 approve the latest draft, which I have uploaded as https://wg5-fortran.org/ARCHIVE/WG23-N1301-20230605.pdf , as "essentially complete" and to give permission to WG23 to complete the document and submit it for ballot as an international standard. I would like this to be one of the resolutions for the Manchester meeting.
> 
> Please let me know if you have questions.
> 
> Steve
> 


--

Cheers!
Dan Nagle



From reubendb at ornl.gov  Mon Jun 12 12:01:20 2023
From: reubendb at ornl.gov (Reuben D. Budiardja)
Date: Mon, 12 Jun 2023 08:01:20 -0400
Subject: [J3] Generics Tutorial at WG5/J3 Joint Meeting This Week
Message-ID: <04635866-1d62-c3e4-0f8e-49b2f9f89b65@ornl.gov>


We plan to have Generics tutorial on Tuesday, Wednesday, Thursday this 
week at 10:45am UK time (GMT+1).

Best,
Reuben

From jehammond at nvidia.com  Wed Jun 14 15:47:47 2023
From: jehammond at nvidia.com (Jeff Hammond)
Date: Wed, 14 Jun 2023 15:47:47 +0000
Subject: [J3] [SC22WG5.6448] 23-196
Message-ID: <DM6PR12MB31301883BCAFDD39368B8B5CCB5AA@DM6PR12MB3130.namprd12.prod.outlook.com>

I like this paper and agree with the choice of %% syntax as well as prohibiting the bypass of use-only.  When I employ ?use, only?, I am hoping that the compiler with be able to reduce compile and link-time because the other symbols are not visible, and %% bypass would break that.

I am sharing my comments here because I don?t attend the relevant subgroup.

Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230614/0728fae3/attachment.htm>

From ondrej at certik.us  Wed Jun 14 18:42:57 2023
From: ondrej at certik.us (=?UTF-8?Q?Ond=C5=99ej_=C4=8Cert=C3=ADk?=)
Date: Wed, 14 Jun 2023 12:42:57 -0600
Subject: [J3] [SC22WG5.6448] 23-196
In-Reply-To: <DM6PR12MB31301883BCAFDD39368B8B5CCB5AA@DM6PR12MB3130.namprd12.prod.outlook.com>
References: <DM6PR12MB31301883BCAFDD39368B8B5CCB5AA@DM6PR12MB3130.namprd12.prod.outlook.com>
Message-ID: <31de89c2-b43c-4bf9-852a-c345f19a2621@app.fastmail.com>

Hi,

Here is the paper: https://j3-fortran.org/doc/year/23/23-196.txt

I think the ideas and the approach there are reasonable. The main use case that seems to be missing is where you want to import the module, but not have any symbols from it imported, only those that you access via `m1%%f`. Example:

    Subroutine s
        Use m1, as_module: ! we have to find a better syntax
        ...
        m1%%f = 999 ! Allowed
        f = 999 ! Not allowed
 
This use case is equivalent to Python's:

import m1
m1.f = 999 # Allowed
f = 999 # Not allowed

It's precisely this use case that has been frequently requested.

Ondrej

On Wed, Jun 14, 2023, at 9:47 AM, Jeff Hammond via J3 wrote:
> I like this paper and agree with the choice of %% syntax as well as 
> prohibiting the bypass of use-only.  When I employ ?use, only?, I am 
> hoping that the compiler with be able to reduce compile and link-time 
> because the other symbols are not visible, and %% bypass would break 
> that.
> 
> I am sharing my comments here because I don?t attend the relevant subgroup.
> 
> Jeff

From steve at stevelionel.com  Wed Jun 14 18:49:53 2023
From: steve at stevelionel.com (Steve Lionel)
Date: Wed, 14 Jun 2023 19:49:53 +0100
Subject: [J3] [SC22WG5.6448] 23-196
In-Reply-To: <31de89c2-b43c-4bf9-852a-c345f19a2621@app.fastmail.com>
References: <DM6PR12MB31301883BCAFDD39368B8B5CCB5AA@DM6PR12MB3130.namprd12.prod.outlook.com>
 <31de89c2-b43c-4bf9-852a-c345f19a2621@app.fastmail.com>
Message-ID: <CAEH1ojOo=bt37kx6i7MhVkKpsaGzMvk9HWeXyyGJur8nMvr3RA@mail.gmail.com>

On Wed, Jun 14, 2023 at 7:43?PM Ond?ej ?ert?k via J3 <
j3 at mailman.j3-fortran.org> wrote:

>
> I think the ideas and the approach there are reasonable. The main use case
> that seems to be missing is where you want to import the module, but not
> have any symbols from it imported, only those that you access via `m1%%f`.
>

Our thought on that is you can say:

import modame, only:

That is, an empty only clause. This makes the module visible but does not
bring in any of its symbols. This is allowed by current syntax. Then you
can use the new feature to reference specific entities.

Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230614/02aaa5a3/attachment.htm>

From ondrej at certik.us  Wed Jun 14 18:42:57 2023
From: ondrej at certik.us (=?UTF-8?Q?Ond=C5=99ej_=C4=8Cert=C3=ADk?=)
Date: Wed, 14 Jun 2023 12:42:57 -0600
Subject: [J3] [SC22WG5.6449]  23-196
In-Reply-To: <DM6PR12MB31301883BCAFDD39368B8B5CCB5AA@DM6PR12MB3130.namprd12.prod.outlook.com>
References: <DM6PR12MB31301883BCAFDD39368B8B5CCB5AA@DM6PR12MB3130.namprd12.prod.outlook.com>
Message-ID: <20230614185052.BBE993591D9@www.open-std.org>

Hi,

Here is the paper: https://j3-fortran.org/doc/year/23/23-196.txt

I think the ideas and the approach there are reasonable. The main use case that seems to be missing is where you want to import the module, but not have any symbols from it imported, only those that you access via `m1%%f`. Example:

    Subroutine s
        Use m1, as_module: ! we have to find a better syntax
        ...
        m1%%f = 999 ! Allowed
        f = 999 ! Not allowed
 
This use case is equivalent to Python's:

import m1
m1.f = 999 # Allowed
f = 999 # Not allowed

It's precisely this use case that has been frequently requested.

Ondrej

On Wed, Jun 14, 2023, at 9:47 AM, Jeff Hammond via J3 wrote:
> I like this paper and agree with the choice of %% syntax as well as 
> prohibiting the bypass of use-only.  When I employ ?use, only?, I am 
> hoping that the compiler with be able to reduce compile and link-time 
> because the other symbols are not visible, and %% bypass would break 
> that.
> 
> I am sharing my comments here because I don?t attend the relevant subgroup.
> 
> Jeff

From ondrej at certik.us  Wed Jun 14 18:53:50 2023
From: ondrej at certik.us (=?UTF-8?Q?Ond=C5=99ej_=C4=8Cert=C3=ADk?=)
Date: Wed, 14 Jun 2023 12:53:50 -0600
Subject: [J3] [SC22WG5.6448] 23-196
In-Reply-To: <CAEH1ojOo=bt37kx6i7MhVkKpsaGzMvk9HWeXyyGJur8nMvr3RA@mail.gmail.com>
References: <DM6PR12MB31301883BCAFDD39368B8B5CCB5AA@DM6PR12MB3130.namprd12.prod.outlook.com>
 <31de89c2-b43c-4bf9-852a-c345f19a2621@app.fastmail.com>
 <CAEH1ojOo=bt37kx6i7MhVkKpsaGzMvk9HWeXyyGJur8nMvr3RA@mail.gmail.com>
Message-ID: <d365cd82-fb60-4384-a2d3-bfbdbfdab9e3@app.fastmail.com>



On Wed, Jun 14, 2023, at 12:49 PM, Steve Lionel via J3 wrote:
> On Wed, Jun 14, 2023 at 7:43?PM Ond?ej ?ert?k via J3 
> <j3 at mailman.j3-fortran.org> wrote:
>> 
>> I think the ideas and the approach there are reasonable. The main use case that seems to be missing is where you want to import the module, but not have any symbols from it imported, only those that you access via `m1%%f`. 
>
> Our thought on that is you can say:
>
> import modame, only:
>
> That is, an empty only clause. This makes the module visible but does 
> not bring in any of its symbols. This is allowed by current syntax. 
> Then you can use the new feature to reference specific entities.

Perfect, this would work!

Ondrej

From steve at stevelionel.com  Wed Jun 14 18:56:34 2023
From: steve at stevelionel.com (Steve Lionel)
Date: Wed, 14 Jun 2023 19:56:34 +0100
Subject: [J3] [SC22WG5.6448] 23-196
In-Reply-To: <d365cd82-fb60-4384-a2d3-bfbdbfdab9e3@app.fastmail.com>
References: <DM6PR12MB31301883BCAFDD39368B8B5CCB5AA@DM6PR12MB3130.namprd12.prod.outlook.com>
 <31de89c2-b43c-4bf9-852a-c345f19a2621@app.fastmail.com>
 <CAEH1ojOo=bt37kx6i7MhVkKpsaGzMvk9HWeXyyGJur8nMvr3RA@mail.gmail.com>
 <d365cd82-fb60-4384-a2d3-bfbdbfdab9e3@app.fastmail.com>
Message-ID: <CAEH1ojMpcUvsZT7fsrDCwb=rGzp_NBQzqYnBok0g7u7H6mwRrg@mail.gmail.com>

Of course, I meant USE, not IMPORT...

Steve

On Wed, Jun 14, 2023 at 7:54?PM Ond?ej ?ert?k <ondrej at certik.us> wrote:

>
>
> On Wed, Jun 14, 2023, at 12:49 PM, Steve Lionel via J3 wrote:
> > On Wed, Jun 14, 2023 at 7:43?PM Ond?ej ?ert?k via J3
> > <j3 at mailman.j3-fortran.org> wrote:
> >>
> >> I think the ideas and the approach there are reasonable. The main use
> case that seems to be missing is where you want to import the module, but
> not have any symbols from it imported, only those that you access via
> `m1%%f`.
> >
> > Our thought on that is you can say:
> >
> > import modame, only:
> >
> > That is, an empty only clause. This makes the module visible but does
> > not bring in any of its symbols. This is allowed by current syntax.
> > Then you can use the new feature to reference specific entities.
>
> Perfect, this would work!
>
> Ondrej
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230614/767afb6a/attachment.htm>

From van.snyder at sbcglobal.net  Wed Jun 14 22:34:59 2023
From: van.snyder at sbcglobal.net (Van Snyder)
Date: Wed, 14 Jun 2023 15:34:59 -0700
Subject: [J3] [SC22WG5.6448] 23-196
In-Reply-To: <31de89c2-b43c-4bf9-852a-c345f19a2621@app.fastmail.com>
References: <DM6PR12MB31301883BCAFDD39368B8B5CCB5AA@DM6PR12MB3130.namprd12.prod.outlook.com>
 <31de89c2-b43c-4bf9-852a-c345f19a2621@app.fastmail.com>
Message-ID: <b01b997981031bbf03c629ace898183bf676efd4.camel@sbcglobal.net>

On Wed, 2023-06-14 at 12:42 -0600, Ond?ej ?ert?k via J3 wrote:
> This use case is equivalent to Python's:
> import m1m1.f = 999 # Allowedf = 999 # Not allowed

And Modula-2. I asked for this in 1986.

In Modula-2, if you use "IMPORT M" you have to qualify every reference,
as M.foo.
If you use "FROM M IMPORT foo" you can use just "foo".

The latter is similar to "USE, ONLY."

As Ond?ej remarks, the former is (still) lacking in Fortran.


I like that dichotomy because by looking at a single file (actually,
two in Modula-2, the interface and implementation modules), I can know
where every identifier comes from without using grep.


Is it too late to make host association work for module names, so that
one percent sign would be enough?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230614/df4581fe/attachment.htm>

From john.reid at stfc.ac.uk  Fri Jun 16 09:20:34 2023
From: john.reid at stfc.ac.uk (John Reid - STFC UKRI)
Date: Fri, 16 Jun 2023 09:20:34 +0000
Subject: [J3] [SC22WG5.6450] Draft minutes
Message-ID: <CWLP265MB10891C6DA4D20536111DBA7DD358A@CWLP265MB1089.GBRP265.PROD.OUTLOOK.COM>

Here are draft minutes of the WG5 meeting. Comments, please. In particular, is the list of participants correct?

John.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230616/44374213/attachment.htm>
-------------- next part --------------
                                        ISO/IEC JTC1/SC22/WG5 N2223-2

Minutes of (Hybrid) Meeting of ISO/IEC JTC1/SC22/WG5
Hosted by BSI, the UK Member Body for JTC1/SC22
Held at Arm Ltd., 11 Portland Street,  Manchester, M1 3HU, UK
June 12-16, 2023.

List of Participants:

Steve Lionel (USA) WG5 convenor
Reinhold Bader (Germany)
Reuben Budiardja (USA)
Kiran Chandramohan (UK)
Daniel Chen (Canada)
Tom Clune (USA)
Malcolm Cohen (UK)
Brian Cornille (USA)
Jeff Hammond (USA)
Magne Haveraaen (Norway)
Paul Henning (USA)
Hidetoshi Iwashita (Japan)
Gary Klimowicz (USA)
Mark LeAir (USA)
Bill Long (USA)
Raghu Maddhipatla (USA)
Lorri Menard (USA)
David Muxworthy (UK)
Lucas Pettey (USA)
John Reid (UK)
Brad Richardson (USA)
Damian Rouson (USA)
Nathan Sircombe (UK)
Jon Steidel (USA)
Masayuki Takata (Japan)

Notes:
1.  This was a joint meeting of SC22/WG5 and INCITS/Fortran. These
    minutes record only the parts of the meeting in WG5 mode.
2.  WG5 papers are referenced as Nnnnn. They are available from
    https://wg5-fortran.org/documents.html
3.  INCITS/Fortran meeting papers are referenced as J3/22-nnn.
    They are available from https://j3-fortran.org/


1. Opening of the Meeting

The meeting opened at 09:05 on Monday, June 12, 2023


2. Opening business

2.1 Introductory remarks from the Convenor

The convenor welcomed both local (in-person) and remote participants
to the meeting.

2.2 Reminder of the ISO Code of Conduct

The convenor reminded participants of the ISO Code of Ethics and Conduct, 
available at
https://www.iso.org/files/live/sites/isoorg/files/store/en/PUB100011.pdf

2.3 Welcome from the Host

Nathan Sircombe welcomed local participants to ARM Office in Manchester.

2.4 Local arrangements

Nathan Sircombe explained the arrangments for the meeting.

2.5 Appointments for this meeting

Drafting Committee: David Muxworthy (chair), Gary Klimowicz,
                    Hidetoshi Iwashita, Reinhold Bader, Daniel Chen.
Librarian: Steve Lionel.
Secretary: John Reid.

2.6 Adoption of the Agenda N2215

The agenda was adopted.
   
   
3. Matters arising from the Minutes of the 2022 meeting (N2202)

Steve Lionel reported that the FDIS was not accepted by the ISO editor 
because of its use of a smaller font than required and because of its use
of a smaller font for deprecated features. At a recent meeting of the 
ISO editor with Steve Lionel and Malcolm Cohen, it was agreed that a 
larger font be used for the next standard and another method be used to 
denote deprecated features. Steve and Malcolm requested that no change 
fonts be made for the 2023 standard and a decision was promised by
16 June. 

Damian Rouson confirmed his offer to host the 2024 meeting at Berkeley 
Labs.


4. Status of 2022 Resolutions (N2200)

Corrigendum 2 has been published. David Muxworthy remarked that ISO had 
made changes, but the document was still correct. However, BSI had 
manually incorporated the changes into a new document labelled Fortran
2023 and made errors. 


5. Reports

5.1 SC22 Matters (Convenor)

Steve Lionel reported that open access to WG5 documents is now provided 
by links to his website. It is no longer available from ISO despite the 
promise that it should continue. 

INCITS now has a rule that no meetings be joint without permission but
we have permission for this meeting to be joint with WG5 and this is 
expected for future meetings. It is clearly needed. 

Drafts of standards up to FDIS may now have paragraph and line numbers. 
WG5 agrees that line numbers should be excluded from the final standard
because they change with translation but requests Steve Lionel to ask
SC22 to seek approval for paragraph numbers to be allowed.

5.2 National Activity Reports

Canada:  No national activity was reported. 
Germany: No national activity was reported. 
Japan:   Masayuki Takata reported that the translation of Fortran
         2018 into Japanese was published in March.
UK:      No national activity was reported. 
USA:     See 5.3.

5.3 Report from Primary Development Body (INCITS/Fortran Chair)

INCITS/Fortran continues to work actively on all aspects of the 
Fortran standard.

5.4 Reports from other Development Bodies (Editors/Heads)

Steve Lionel, Tom Clune, and John Reid have been meeting every 2 weeks 
on zoom with Stephen Michell and Erhard Ploedereder of WG23 constructing
a supplementary standard on vulnerabilities in Fortran. The latest draft 
is nearly ready for submission. 

5.5 Liaison Reports:

Liaison reports were presented under INCITS/Fortran business.


6. WG5 Business and Strategic Plans

6.1 Goals for 2023-2025

The intention remains that the next revision of the standard be published
before the end of 2028. The target dates shown in N2200 were agreed.


7. Create initial work item list for the next revision ("202Y")

The list of items in N2222 was agreed. 
 
 
8. Closing Business

8.1 Future meetings

The next meeting will be in Berkeley, Ca, USA, hosted by Damian Rouson. 
The dates are expected to be 24-28 June 2023 and are subject to confirmation. 

A preliminary offer to host the 2025 in Helsinki has been made by Jeff Hammond.


8.2 Any other business

There was no other business.

9. Adoption of Resolutions

The resolutions in N2023 were all adopted unanimously.

10. Adjournment

The meeting was closed at 10:07, June 16, 2023.

From Reinhold.Bader at lrz.de  Fri Jun 16 09:54:56 2023
From: Reinhold.Bader at lrz.de (Bader, Reinhold)
Date: Fri, 16 Jun 2023 09:54:56 +0000
Subject: [J3] [SC22WG5.6451] AW: Draft minutes
In-Reply-To: <CWLP265MB10891C6DA4D20536111DBA7DD358A@CWLP265MB1089.GBRP265.PROD.OUTLOOK.COM>
References: <CWLP265MB10891C6DA4D20536111DBA7DD358A@CWLP265MB1089.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <20230616100012.2BC233591C0@www.open-std.org>

John,

in section 9, the resolution document name needs to be updated to N2219.

Was there already feedback from ISO as promised in 3? If yes, perhaps a remark on this can be added.

Cheers,
Reinhold

Von: owner-sc22wg5 at open-std.org <owner-sc22wg5 at open-std.org> Im Auftrag von John Reid - STFC UKRI
Gesendet: Freitag, 16. Juni 2023 11:21
An: WG5 List <sc22wg5 at open-std.org>
Betreff: [SC22WG5.6450] Draft minutes

Here are draft minutes of the WG5 meeting. Comments, please. In particular, is the list of participants correct?

John.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230616/56885b51/attachment.htm>

From steve at stevelionel.com  Fri Jun 16 10:06:26 2023
From: steve at stevelionel.com (Steve Lionel)
Date: Fri, 16 Jun 2023 11:06:26 +0100
Subject: [J3] [SC22WG5.6452]  AW: Draft minutes
In-Reply-To: <20230616100012.2BC233591C0@www.open-std.org>
References: <CWLP265MB10891C6DA4D20536111DBA7DD358A@CWLP265MB1089.GBRP265.PROD.OUTLOOK.COM>
 <20230616100012.2BC233591C0@www.open-std.org>
Message-ID: <20230616100639.711F13591E4@www.open-std.org>

Sadly, no response yet from ISO.

Steve

On Fri, Jun 16, 2023 at 11:00?AM Bader, Reinhold via J3 <
j3 at mailman.j3-fortran.org> wrote:

> John,
>
>
>
> in section 9, the resolution document name needs to be updated to N2219.
>
>
>
> Was there already feedback from ISO as promised in 3? If yes, perhaps a
> remark on this can be added.
>
>
>
> Cheers,
>
> Reinhold
>
>
>
> *Von:* owner-sc22wg5 at open-std.org <owner-sc22wg5 at open-std.org> *Im
> Auftrag von *John Reid - STFC UKRI
> *Gesendet:* Freitag, 16. Juni 2023 11:21
> *An:* WG5 List <sc22wg5 at open-std.org>
> *Betreff:* [SC22WG5.6450] Draft minutes
>
>
>
> Here are draft minutes of the WG5 meeting. Comments, please. In
> particular, is the list of participants correct?
>
>
>
> John.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230616/2da2e2dc/attachment-0001.htm>

From gak at dancingbear.dev  Fri Jun 16 17:54:51 2023
From: gak at dancingbear.dev (Gary Klimowicz)
Date: Fri, 16 Jun 2023 10:54:51 -0700
Subject: [J3] [SC22WG5.6450] Draft minutes
In-Reply-To: <CWLP265MB10891C6DA4D20536111DBA7DD358A@CWLP265MB1089.GBRP265.PROD.OUTLOOK.COM>
References: <CWLP265MB10891C6DA4D20536111DBA7DD358A@CWLP265MB1089.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <21AF8C68-7193-4D5C-8FC9-1C2BF389E564@dancingbear.dev>

Hi, John.

I believe Aleksander Donev (US) attended briefly, at least on Thursday. I didn't see him in the attendee list. Aleks is one of my alternates.

Thanks for doing the minutes.

Gary


> On Jun 16, 2023, at 02:20, John Reid - STFC UKRI via J3 <j3 at mailman.j3-fortran.org> wrote:
> 
> Here are draft minutes of the WG5 meeting. Comments, please. In particular, is the list of participants correct?
> 
> John. 
> <minutes23.txt>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230616/1542266d/attachment.htm>

From gak at dancingbear.dev  Fri Jun 16 17:54:51 2023
From: gak at dancingbear.dev (Gary Klimowicz)
Date: Fri, 16 Jun 2023 10:54:51 -0700
Subject: [J3] [SC22WG5.6453]  Draft minutes
In-Reply-To: <CWLP265MB10891C6DA4D20536111DBA7DD358A@CWLP265MB1089.GBRP265.PROD.OUTLOOK.COM>
References: <CWLP265MB10891C6DA4D20536111DBA7DD358A@CWLP265MB1089.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <20230616180122.37DEB3591E7@www.open-std.org>

Hi, John.

I believe Aleksander Donev (US) attended briefly, at least on Thursday. I didn't see him in the attendee list. Aleks is one of my alternates.

Thanks for doing the minutes.

Gary


> On Jun 16, 2023, at 02:20, John Reid - STFC UKRI via J3 <j3 at mailman.j3-fortran.org> wrote:
> 
> Here are draft minutes of the WG5 meeting. Comments, please. In particular, is the list of participants correct?
> 
> John. 
> <minutes23.txt>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230616/9df63a10/attachment.htm>

From richard at bleikamp.net  Fri Jun 16 18:15:58 2023
From: richard at bleikamp.net (Richard Bleikamp)
Date: Fri, 16 Jun 2023 14:15:58 -0400
Subject: [J3] [SC22WG5.6450] Draft minutes
In-Reply-To: <CWLP265MB10891C6DA4D20536111DBA7DD358A@CWLP265MB1089.GBRP265.PROD.OUTLOOK.COM>
References: <CWLP265MB10891C6DA4D20536111DBA7DD358A@CWLP265MB1089.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <956b35e4-5dc1-f5f7-dde3-9306a003d726@bleikamp.net>

Hi John,

Should the "Future meeting" in Berkeley be in 2024?


rich

On 6/16/2023 5:20 AM, John Reid - STFC UKRI via J3 wrote:
> Here are draft minutes of the WG5 meeting. Comments, please. In 
> particular, is the list of participants correct?
>
> John.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230616/33fb8d00/attachment.htm>

From gak at dancingbear.dev  Fri Jun 16 18:19:59 2023
From: gak at dancingbear.dev (Gary Klimowicz)
Date: Fri, 16 Jun 2023 11:19:59 -0700
Subject: [J3] [SC22WG5.6453]  Draft minutes
In-Reply-To: <MW4PR84MB18513D123B45F6275BE3CF319758A@MW4PR84MB1851.NAMPRD84.PROD.OUTLOOK.COM>
References: <CWLP265MB10891C6DA4D20536111DBA7DD358A@CWLP265MB1089.GBRP265.PROD.OUTLOOK.COM>
 <20230616180122.37DEB3591E7@www.open-std.org>
 <MW4PR84MB18513D123B45F6275BE3CF319758A@MW4PR84MB1851.NAMPRD84.PROD.OUTLOOK.COM>
Message-ID: <ED7A964A-6C81-4266-8651-9E9F74071F57@dancingbear.dev>

Thanks, Bill. Aleks has been too polite to correct me. :-)



> On Jun 16, 2023, at 11:18, Long, Bill F <william.long at hpe.com> wrote:
> 
> Yes, I saw him on the Zoom screen.  The correct spelling of his first name is Aleksandar (second to last letter is an "a"). 
> 
> Cheer,
> Bill
> 
> From: J3 <j3-bounces at mailman.j3-fortran.org> on behalf of Gary Klimowicz via J3 <j3 at mailman.j3-fortran.org>
> Sent: Friday, June 16, 2023 12:54 PM
> To: General J3 interest list <j3 at mailman.j3-fortran.org>
> Cc: Gary Klimowicz <gak at dancingbear.dev>; WG5 List <sc22wg5 at open-std.org>
> Subject: [J3] [SC22WG5.6453] Draft minutes
>  
> Hi, John.
> 
> I believe Aleksander Donev (US) attended briefly, at least on Thursday. I didn't see him in the attendee list. Aleks is one of my alternates.
> 
> Thanks for doing the minutes.
> 
> Gary
> 
> 
>> On Jun 16, 2023, at 02:20, John Reid - STFC UKRI via J3 <j3 at mailman.j3-fortran.org> wrote:
>> 
>> Here are draft minutes of the WG5 meeting. Comments, please. In particular, is the list of participants correct?
>> 
>> John. 
>> <minutes23.txt>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230616/fc887892/attachment.htm>

From gak at dancingbear.dev  Fri Jun 16 18:19:59 2023
From: gak at dancingbear.dev (Gary Klimowicz)
Date: Fri, 16 Jun 2023 11:19:59 -0700
Subject: [J3] [SC22WG5.6454]   Draft minutes
In-Reply-To: <MW4PR84MB18513D123B45F6275BE3CF319758A@MW4PR84MB1851.NAMPRD84.PROD.OUTLOOK.COM>
References: <CWLP265MB10891C6DA4D20536111DBA7DD358A@CWLP265MB1089.GBRP265.PROD.OUTLOOK.COM>
 <20230616180122.37DEB3591E7@www.open-std.org>
 <MW4PR84MB18513D123B45F6275BE3CF319758A@MW4PR84MB1851.NAMPRD84.PROD.OUTLOOK.COM>
Message-ID: <20230616182033.D61523591E8@www.open-std.org>

Thanks, Bill. Aleks has been too polite to correct me. :-)



> On Jun 16, 2023, at 11:18, Long, Bill F <william.long at hpe.com> wrote:
> 
> Yes, I saw him on the Zoom screen.  The correct spelling of his first name is Aleksandar (second to last letter is an "a"). 
> 
> Cheer,
> Bill
> 
> From: J3 <j3-bounces at mailman.j3-fortran.org> on behalf of Gary Klimowicz via J3 <j3 at mailman.j3-fortran.org>
> Sent: Friday, June 16, 2023 12:54 PM
> To: General J3 interest list <j3 at mailman.j3-fortran.org>
> Cc: Gary Klimowicz <gak at dancingbear.dev>; WG5 List <sc22wg5 at open-std.org>
> Subject: [J3] [SC22WG5.6453] Draft minutes
>  
> Hi, John.
> 
> I believe Aleksander Donev (US) attended briefly, at least on Thursday. I didn't see him in the attendee list. Aleks is one of my alternates.
> 
> Thanks for doing the minutes.
> 
> Gary
> 
> 
>> On Jun 16, 2023, at 02:20, John Reid - STFC UKRI via J3 <j3 at mailman.j3-fortran.org> wrote:
>> 
>> Here are draft minutes of the WG5 meeting. Comments, please. In particular, is the list of participants correct?
>> 
>> John. 
>> <minutes23.txt>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230616/1b69ecea/attachment-0001.htm>

From john.reid at stfc.ac.uk  Fri Jun 16 20:32:19 2023
From: john.reid at stfc.ac.uk (John Reid - STFC UKRI)
Date: Fri, 16 Jun 2023 20:32:19 +0000
Subject: [J3] [SC22WG5.6454]   Draft minutes
In-Reply-To: <20230616182033.D61523591E8@www.open-std.org>
References: <CWLP265MB10891C6DA4D20536111DBA7DD358A@CWLP265MB1089.GBRP265.PROD.OUTLOOK.COM>
 <20230616180122.37DEB3591E7@www.open-std.org>
 <MW4PR84MB18513D123B45F6275BE3CF319758A@MW4PR84MB1851.NAMPRD84.PROD.OUTLOOK.COM>
 <20230616182033.D61523591E8@www.open-std.org>
Message-ID: <LO2P265MB1104BBE82F0B27D3346EF5F5D358A@LO2P265MB1104.GBRP265.PROD.OUTLOOK.COM>

I have added him.

Cheers,

John.
________________________________
From: J3 <j3-bounces at mailman.j3-fortran.org> on behalf of Gary Klimowicz via J3 <j3 at mailman.j3-fortran.org>
Sent: 16 June 2023 19:19
To: Long, Bill F <william.long at hpe.com>
Cc: Gary Klimowicz <gak at dancingbear.dev>; General J3 interest list <j3 at mailman.j3-fortran.org>; WG5 List <sc22wg5 at open-std.org>
Subject: [J3] [SC22WG5.6454] Draft minutes

Thanks, Bill. Aleks has been too polite to correct me. :-)



On Jun 16, 2023, at 11:18, Long, Bill F <william.long at hpe.com> wrote:

Yes, I saw him on the Zoom screen.  The correct spelling of his first name is Aleksandar (second to last letter is an "a").

Cheer,
Bill

________________________________
From: J3 <j3-bounces at mailman.j3-fortran.org> on behalf of Gary Klimowicz via J3 <j3 at mailman.j3-fortran.org>
Sent: Friday, June 16, 2023 12:54 PM
To: General J3 interest list <j3 at mailman.j3-fortran.org>
Cc: Gary Klimowicz <gak at dancingbear.dev>; WG5 List <sc22wg5 at open-std.org>
Subject: [J3] [SC22WG5.6453] Draft minutes

Hi, John.

I believe Aleksander Donev (US) attended briefly, at least on Thursday. I didn't see him in the attendee list. Aleks is one of my alternates.

Thanks for doing the minutes.

Gary


On Jun 16, 2023, at 02:20, John Reid - STFC UKRI via J3 <j3 at mailman.j3-fortran.org> wrote:

Here are draft minutes of the WG5 meeting. Comments, please. In particular, is the list of participants correct?

John.
<minutes23.txt>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230616/08225e13/attachment.htm>

From john.reid at stfc.ac.uk  Fri Jun 16 20:32:19 2023
From: john.reid at stfc.ac.uk (John Reid - STFC UKRI)
Date: Fri, 16 Jun 2023 20:32:19 +0000
Subject: [J3] [SC22WG5.6456]    Draft minutes
In-Reply-To: <20230616182033.D61523591E8@www.open-std.org>
References: <CWLP265MB10891C6DA4D20536111DBA7DD358A@CWLP265MB1089.GBRP265.PROD.OUTLOOK.COM>
 <20230616180122.37DEB3591E7@www.open-std.org>
 <MW4PR84MB18513D123B45F6275BE3CF319758A@MW4PR84MB1851.NAMPRD84.PROD.OUTLOOK.COM>
 <20230616182033.D61523591E8@www.open-std.org>
Message-ID: <LO2P265MB1104BBE82F0B27D3346EF5F5D358A@LO2P265MB1104.GBRP265.PROD.OUTLOOK.COM>

I have added him.

Cheers,

John.
________________________________
From: J3 <j3-bounces at mailman.j3-fortran.org> on behalf of Gary Klimowicz via J3 <j3 at mailman.j3-fortran.org>
Sent: 16 June 2023 19:19
To: Long, Bill F <william.long at hpe.com>
Cc: Gary Klimowicz <gak at dancingbear.dev>; General J3 interest list <j3 at mailman.j3-fortran.org>; WG5 List <sc22wg5 at open-std.org>
Subject: [J3] [SC22WG5.6454] Draft minutes

Thanks, Bill. Aleks has been too polite to correct me. :-)



On Jun 16, 2023, at 11:18, Long, Bill F <william.long at hpe.com> wrote:

Yes, I saw him on the Zoom screen.  The correct spelling of his first name is Aleksandar (second to last letter is an "a").

Cheer,
Bill

________________________________
From: J3 <j3-bounces at mailman.j3-fortran.org> on behalf of Gary Klimowicz via J3 <j3 at mailman.j3-fortran.org>
Sent: Friday, June 16, 2023 12:54 PM
To: General J3 interest list <j3 at mailman.j3-fortran.org>
Cc: Gary Klimowicz <gak at dancingbear.dev>; WG5 List <sc22wg5 at open-std.org>
Subject: [J3] [SC22WG5.6453] Draft minutes

Hi, John.

I believe Aleksander Donev (US) attended briefly, at least on Thursday. I didn't see him in the attendee list. Aleks is one of my alternates.

Thanks for doing the minutes.

Gary


On Jun 16, 2023, at 02:20, John Reid - STFC UKRI via J3 <j3 at mailman.j3-fortran.org> wrote:

Here are draft minutes of the WG5 meeting. Comments, please. In particular, is the list of participants correct?

John.
<minutes23.txt>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20230616/08225e13/attachment-0003.htm>

From steve at stevelionel.com  Wed Jun 21 23:04:00 2023
From: steve at stevelionel.com (Steve Lionel)
Date: Wed, 21 Jun 2023 19:04:00 -0400
Subject: [J3] [SC22WG5.6460] This time for sure!
Message-ID: <20230621230404.91EDD3591D8@www.open-std.org>

The revised F2023 FDIS, with changes requested by ISO and a waiver for 
the font and font sizes (received yesterday), has been submitted to ISO. 
There is an eight-week voting period (though I imagine the ISO editor 
will take a look first.) If everything goes well, it may publish in 
September or October.

Thanks to everyone who helped make this happen, especially Malcolm, who 
put in extraordinary effort in response to the ISO editor's comments.

Steve


From gak at dancingbear.dev  Thu Jun 22 04:22:04 2023
From: gak at dancingbear.dev (Gary Klimowicz)
Date: Wed, 21 Jun 2023 21:22:04 -0700
Subject: [J3] [SC22WG5.6460] This time for sure!
In-Reply-To: <20230621230404.91EDD3591D8@www.open-std.org>
References: <20230621230404.91EDD3591D8@www.open-std.org>
Message-ID: <29B8C345-9A63-42F2-B5DB-9EEF31BB402F@dancingbear.dev>

On Jun 21, 2023, at 16:04, Steve Lionel via J3 <j3 at mailman.j3-fortran.org> wrote:
> 
> The revised F2023 FDIS, with changes requested by ISO and a waiver for the font and font sizes (received yesterday), has been submitted to ISO. There is an eight-week voting period (though I imagine the ISO editor will take a look first.) If everything goes well, it may publish in September or October.
> 
> Thanks to everyone who helped make this happen, especially Malcolm, who put in extraordinary effort in response to the ISO editor's comments.

This is great news, Steve! Thanks to Malcolm for all his work, and to you for pushing this through.


From gak at dancingbear.dev  Thu Jun 22 04:22:04 2023
From: gak at dancingbear.dev (Gary Klimowicz)
Date: Wed, 21 Jun 2023 21:22:04 -0700
Subject: [J3] [SC22WG5.6461]  This time for sure!
In-Reply-To: <20230621230404.91EDD3591D8@www.open-std.org>
References: <20230621230404.91EDD3591D8@www.open-std.org>
Message-ID: <20230622043153.75DCF3591E4@www.open-std.org>

On Jun 21, 2023, at 16:04, Steve Lionel via J3 <j3 at mailman.j3-fortran.org> wrote:
> 
> The revised F2023 FDIS, with changes requested by ISO and a waiver for the font and font sizes (received yesterday), has been submitted to ISO. There is an eight-week voting period (though I imagine the ISO editor will take a look first.) If everything goes well, it may publish in September or October.
> 
> Thanks to everyone who helped make this happen, especially Malcolm, who put in extraordinary effort in response to the ISO editor's comments.

This is great news, Steve! Thanks to Malcolm for all his work, and to you for pushing this through.


From reubendb at ornl.gov  Thu Jun 22 14:27:27 2023
From: reubendb at ornl.gov (Reuben D. Budiardja)
Date: Thu, 22 Jun 2023 10:27:27 -0400
Subject: [J3] [EXTERNAL]  [SC22WG5.6461] This time for sure!
In-Reply-To: <20230622043153.75DCF3591E4@www.open-std.org>
References: <20230621230404.91EDD3591D8@www.open-std.org>
 <20230622043153.75DCF3591E4@www.open-std.org>
Message-ID: <30d5ea6d-5b7d-099f-c435-8ff1b6261a7c@ornl.gov>

Great news indeed. Thank you to Malcolm and Steve for pushing this.

And thank you for everyone's hard work. We had a very productive meeting 
last week.

Best,
Reuben

On 6/22/23 00:22, Gary Klimowicz via J3 wrote:
> On Jun 21, 2023, at 16:04, Steve Lionel via J3 <j3 at mailman.j3-fortran.org> wrote:
>>
>> The revised F2023 FDIS, with changes requested by ISO and a waiver for the font and font sizes (received yesterday), has been submitted to ISO. There is an eight-week voting period (though I imagine the ISO editor will take a look first.) If everything goes well, it may publish in September or October.
>>
>> Thanks to everyone who helped make this happen, especially Malcolm, who put in extraordinary effort in response to the ISO editor's comments.
> 
> This is great news, Steve! Thanks to Malcolm for all his work, and to you for pushing this through.
> 


From reubendb at ornl.gov  Thu Jun 22 14:27:27 2023
From: reubendb at ornl.gov (Reuben D. Budiardja)
Date: Thu, 22 Jun 2023 10:27:27 -0400
Subject: [J3] [SC22WG5.6462] [EXTERNAL]  This time for sure!
In-Reply-To: <20230622043153.75DCF3591E4@www.open-std.org>
References: <20230621230404.91EDD3591D8@www.open-std.org>
 <20230622043153.75DCF3591E4@www.open-std.org>
Message-ID: <20230622144215.0625F3591EC@www.open-std.org>

Great news indeed. Thank you to Malcolm and Steve for pushing this.

And thank you for everyone's hard work. We had a very productive meeting 
last week.

Best,
Reuben

On 6/22/23 00:22, Gary Klimowicz via J3 wrote:
> On Jun 21, 2023, at 16:04, Steve Lionel via J3 <j3 at mailman.j3-fortran.org> wrote:
>>
>> The revised F2023 FDIS, with changes requested by ISO and a waiver for the font and font sizes (received yesterday), has been submitted to ISO. There is an eight-week voting period (though I imagine the ISO editor will take a look first.) If everything goes well, it may publish in September or October.
>>
>> Thanks to everyone who helped make this happen, especially Malcolm, who put in extraordinary effort in response to the ISO editor's comments.
> 
> This is great news, Steve! Thanks to Malcolm for all his work, and to you for pushing this through.
>