Hello.

I recently looked at P0067R4 (Elementary string conversions, revision 4),
especially the versions that take a base argument, and noticed that the
interfaces specified in that paper would work equally well in C if one
replaces the std::error_code member in the result of from_string with an
int that contains 0, EINVAL or ERANGE.

Now, the embarrasment that the paper sets out to address exist in C just as
much as in C++, even if they have slightly fewer old ways to do it, so,
have there been any interest from WG14 in it?

Are they even aware of it?

Additionally, have there been any more forward progress with this since Oulo,
like it beeing included in the current committe draft? (R3 is listed as
adopted but not R4)

/MF

--
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/20161119215957.GA18472%40noemi.

.

------=_Part_7531_1419003044.1479596259652
Content-Type: multipart/alternative;
 boundary="----=_Part_7532_810861540.1479596259653"

------=_Part_7532_810861540.1479596259653
Content-Type: text/plain; charset=UTF-8



On Saturday, November 19, 2016 at 5:00:00 PM UTC-5, Magnus Fromreide wrote:
>
> Hello.
>
> I recently looked at P0067R4 (Elementary string conversions, revision 4),
> especially the versions that take a base argument, and noticed that the
> interfaces specified in that paper would work equally well in C if one
> replaces the std::error_code member in the result of from_string with an
> int that contains 0, EINVAL or ERANGE.
>
> Now, the embarrasment that the paper sets out to address exist in C just
> as
> much as in C++, even if they have slightly fewer old ways to do it, so,
> have there been any interest from WG14 in it?
>
> Are they even aware of it?
>
> Additionally, have there been any more forward progress with this since
> Oulo,
> like it beeing included in the current committe draft? (R3 is listed as
> adopted but not R4)
>

R4 seems to just be bug fixes in the wording.

--
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/a94107ee-4ed4-42fd-8946-599ad0d33437%40isocpp.org.

------=_Part_7532_810861540.1479596259653
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><br>On Saturday, November 19, 2016 at 5:00:00 PM UTC-5=
, Magnus Fromreide wrote:<blockquote class=3D"gmail_quote" style=3D"margin:=
 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">Hello=
..
<br>
<br>I recently looked at P0067R4 (Elementary string conversions, revision 4=
),
<br>especially the versions that take a base argument, and noticed that the
<br>interfaces specified in that paper would work equally well in C if one
<br>replaces the std::error_code member in the result of from_string with a=
n
<br>int that contains 0, EINVAL or ERANGE.
<br>
<br>Now, the embarrasment that the paper sets out to address exist in C jus=
t as
<br>much as in C++, even if they have slightly fewer old ways to do it, so,
<br>have there been any interest from WG14 in it?
<br>
<br>Are they even aware of it?
<br>
<br>Additionally, have there been any more forward progress with this since=
 Oulo,
<br>like it beeing included in the current committe draft? (R3 is listed as
<br>adopted but not R4)
<br></blockquote><div><br>R4 seems to just be bug fixes in the wording.<br>=
</div></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; 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/a94107ee-4ed4-42fd-8946-599ad0d33437%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/a94107ee-4ed4-42fd-8946-599ad0d33437=
%40isocpp.org</a>.<br />

------=_Part_7532_810861540.1479596259653--

------=_Part_7531_1419003044.1479596259652--

.

P0067R3 was adopted in Oulu, but the Project Editor found serious
bugs in the wording.

P0067R4 fixes those bugs.

P0067R5 has a slight interface update and was adopted in Issaquah.
It should land in the post-Issaquah working draft.

As far as C is concerned: If they're interested, they're welcome
to adopt the facility in some way or another.

Jens



On 2016-11-19 22:59, Magnus Fromreide wrote:
> Hello.
>
> I recently looked at P0067R4 (Elementary string conversions, revision 4),
> especially the versions that take a base argument, and noticed that the
> interfaces specified in that paper would work equally well in C if one
> replaces the std::error_code member in the result of from_string with an
> int that contains 0, EINVAL or ERANGE.
>
> Now, the embarrasment that the paper sets out to address exist in C just as
> much as in C++, even if they have slightly fewer old ways to do it, so,
> have there been any interest from WG14 in it?
>
> Are they even aware of it?
>
> Additionally, have there been any more forward progress with this since Oulo,
> like it beeing included in the current committe draft? (R3 is listed as
> adopted but not R4)
>
> /MF
>

--
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/ebc6f4d1-d6c9-3af9-fa66-6c0e5aabe10e%40gmx.net.

.