------=_Part_2244_2116357960.1476543674242
Content-Type: multipart/alternative;
 boundary="----=_Part_2245_170172754.1476543674242"

------=_Part_2245_170172754.1476543674242
Content-Type: text/plain; charset=UTF-8

Inspired by the CppCon 2016 talks about embedded programming and convincing
embedded programmers that C++ is a better choice, I was wondering if it was
worth updating the stuff in the <c*> headers to be more RAII and type
friendly to make the convincing/conversion process easier. Not replacing
things, but perhaps creating C++ analogs of those C features and making
them safe and generic. Simple stuff, like wrapping FILE* into a shallow
RAII non-copyable type, to wrapping functions that use/produce void* data
to hide details like size, to creating overloaded versions of the math
functions rather than having to write the type specific calls, to hairy
stuff like variadic templatizing xprintfs and such.

--
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/fd06c458-ef97-4c05-bbad-b62587c9cd3d%40isocpp.org.

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

<div dir=3D"ltr">Inspired by the CppCon 2016 talks about embedded programmi=
ng and convincing embedded programmers that C++ is a better choice, I was w=
ondering if it was worth updating the stuff in the &lt;c*&gt; headers to be=
 more RAII and type friendly to make the convincing/conversion process easi=
er. Not replacing things, but perhaps creating C++ analogs of those C featu=
res and making them safe and generic. Simple stuff, like wrapping FILE* int=
o a shallow RAII non-copyable type, to wrapping functions that use/produce =
void* data to hide details like size, to creating overloaded versions of th=
e math functions rather than having to write the type specific calls, to ha=
iry stuff like variadic templatizing xprintfs and such.<br></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/fd06c458-ef97-4c05-bbad-b62587c9cd3d%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/fd06c458-ef97-4c05-bbad-b62587c9cd3d=
%40isocpp.org</a>.<br />

------=_Part_2245_170172754.1476543674242--

------=_Part_2244_2116357960.1476543674242--

.