Date: Mon, 11 Oct 2021 22:03:58 +0000
Hey,
The proposed changes to fopen 'a' seem reasonable for us to implement. We're mostly concerned with preserving backwards compatibility, and I don't see any major impact from ensuring the file access is atomic.
I want to note though that the UCRT does implement fopen 'x' (the paper claims it isn't implemented). This hasn't always been the case, but support was added in 2017 and backported to all our UCRT versions. Other Microsoft CRTs, however, do not have this feature.
Thanks,
Steve
From: Casey Carter <cartec69_at_[hidden]>
Sent: Monday, October 11, 2021 2:54 PM
To: liaison_at_[hidden]; Steve Wishnousky <stwish_at_[hidden]>
Cc: Niall Douglas <s_sourceforge_at_[hidden]>
Subject: Re: [wg14/wg21 liaison] WG14 N2830 fopen('x') and fopen('a')
+Steve for UCRT feedback
On Mon, Oct 11, 2021 at 6:13 AM Niall Douglas via Liaison <liaison_at_[hidden]<mailto:liaison_at_[hidden]>> wrote:
CC: Mr. Wakely
To our WG21 colleagues, please find attached for your information WG14
N2830 fopen('x') and fopen('a') which proposes strengthened wording for
those two operations, which in turn may affect C++ iostreams.
I would once again ask that a maintainer of Microsoft's UCRT get in
touch, as theirs is the only implementation of fopen('a') which I
reviewed which is not atomic (and for no good reason, as Win32
implements it perfectly well).
Niall
_______________________________________________
Liaison mailing list
Liaison_at_[hidden]<mailto:Liaison_at_[hidden]>
Subscription: https://lists.isocpp.org/mailman/listinfo.cgi/liaison<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isocpp.org%2Fmailman%2Flistinfo.cgi%2Fliaison&data=04%7C01%7Cstwish%40microsoft.com%7Ca5fe6b60b24442f6f6f208d98d019a49%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637695860917491500%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Jne%2BSdSwSqiOGS58V4%2B%2BQiBeQu7cvMDgjbLbdSeVj3Q%3D&reserved=0>
Link to this post: http://lists.isocpp.org/liaison/2021/10/0886.php<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.isocpp.org%2Fliaison%2F2021%2F10%2F0886.php&data=04%7C01%7Cstwish%40microsoft.com%7Ca5fe6b60b24442f6f6f208d98d019a49%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637695860917501453%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=kZ4toBhLnIRAn1kL1TvIZU%2BJBe5NnHaL8MDy%2BKt6rhE%3D&reserved=0>
The proposed changes to fopen 'a' seem reasonable for us to implement. We're mostly concerned with preserving backwards compatibility, and I don't see any major impact from ensuring the file access is atomic.
I want to note though that the UCRT does implement fopen 'x' (the paper claims it isn't implemented). This hasn't always been the case, but support was added in 2017 and backported to all our UCRT versions. Other Microsoft CRTs, however, do not have this feature.
Thanks,
Steve
From: Casey Carter <cartec69_at_[hidden]>
Sent: Monday, October 11, 2021 2:54 PM
To: liaison_at_[hidden]; Steve Wishnousky <stwish_at_[hidden]>
Cc: Niall Douglas <s_sourceforge_at_[hidden]>
Subject: Re: [wg14/wg21 liaison] WG14 N2830 fopen('x') and fopen('a')
+Steve for UCRT feedback
On Mon, Oct 11, 2021 at 6:13 AM Niall Douglas via Liaison <liaison_at_[hidden]<mailto:liaison_at_[hidden]>> wrote:
CC: Mr. Wakely
To our WG21 colleagues, please find attached for your information WG14
N2830 fopen('x') and fopen('a') which proposes strengthened wording for
those two operations, which in turn may affect C++ iostreams.
I would once again ask that a maintainer of Microsoft's UCRT get in
touch, as theirs is the only implementation of fopen('a') which I
reviewed which is not atomic (and for no good reason, as Win32
implements it perfectly well).
Niall
_______________________________________________
Liaison mailing list
Liaison_at_[hidden]<mailto:Liaison_at_[hidden]>
Subscription: https://lists.isocpp.org/mailman/listinfo.cgi/liaison<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isocpp.org%2Fmailman%2Flistinfo.cgi%2Fliaison&data=04%7C01%7Cstwish%40microsoft.com%7Ca5fe6b60b24442f6f6f208d98d019a49%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637695860917491500%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Jne%2BSdSwSqiOGS58V4%2B%2BQiBeQu7cvMDgjbLbdSeVj3Q%3D&reserved=0>
Link to this post: http://lists.isocpp.org/liaison/2021/10/0886.php<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.isocpp.org%2Fliaison%2F2021%2F10%2F0886.php&data=04%7C01%7Cstwish%40microsoft.com%7Ca5fe6b60b24442f6f6f208d98d019a49%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637695860917501453%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=kZ4toBhLnIRAn1kL1TvIZU%2BJBe5NnHaL8MDy%2BKt6rhE%3D&reserved=0>
Received on 2021-10-11 17:04:04