Topic: on P1283R0 [[shared]]
Author: pasa@lib.hu
Date: Fri, 26 Oct 2018 17:17:23 -0700 (PDT)
Raw View
------=_Part_186_1186437296.1540599443534
Content-Type: multipart/alternative;
boundary="----=_Part_187_2045534025.1540599443534"
------=_Part_187_2045534025.1540599443534
Content-Type: text/plain; charset="UTF-8"
in p1283r0
<http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1283r0.html> the
author states "Platforms that might have required a difference are no
longer supported by their vendors, and have instead added support for a
single export."
I found no evidence to this claim. For example MSDN
<https://docs.microsoft.com/en-us/cpp/build/importing-and-exporting?view=vs-2017>
says to use import just as we did in the past to get the most efficient
code, and it has impact on the object and resulting DLL too.
So if such attribute is considered for the standard it should be one that
is capable replacing its current nonstandard notation, and a single-word
variant will not do.
--
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/eceb8a52-f615-4eac-9374-fa66a7d4b33a%40isocpp.org.
------=_Part_187_2045534025.1540599443534
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>in <a href=3D"http://www.open-std.org/jtc1/sc22/wg21/=
docs/papers/2018/p1283r0.html">p1283r0</a> the author states "Platform=
s that might have required a difference
are no longer supported by their vendors, and have instead added support fo=
r a
single export."</div><div><br></div><div>I found no evidence to this c=
laim. For example <a href=3D"https://docs.microsoft.com/en-us/cpp/build/imp=
orting-and-exporting?view=3Dvs-2017">MSDN</a> says to use import just as we=
did in the past to get the most efficient code, and it has impact on the o=
bject and resulting DLL too. <br></div><div><br></div><div>So if such attri=
bute is considered for the standard it should be one that is capable replac=
ing its current nonstandard notation, and a single-word variant will not do=
..</div><div><br></div><div><br></div></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/eceb8a52-f615-4eac-9374-fa66a7d4b33a%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/eceb8a52-f615-4eac-9374-fa66a7d4b33a=
%40isocpp.org</a>.<br />
------=_Part_187_2045534025.1540599443534--
------=_Part_186_1186437296.1540599443534--
.