[prev in list] [next in list] [prev in thread] [next in thread]
List: zeromq-dev
Subject: Re: [zeromq-dev] Porting libzmq to C++17
From: "Jens Auer" <jens.auer () betaversion ! net>
Date: 2017-05-22 19:01:33
Message-ID: 00c801d2d32d$d5a2efe0$80e8cfa0$ () betaversion ! net
[Download RAW message or body]
This is a multipart message in MIME format.
[Attachment #2 (multipart/alternative)]
This is a multipart message in MIME format.
Hi,
I don't think it is just syntactic sugar, even if the changes are not what I was \
hoping for. Inline variables and guaranteed copy elision are semantic changes, so \
there are some non-syntactic features. Most changes are small, but I think they will \
have significant impact on the way that modern C++ is written. I am thinking \
especially of structured bindings and the template deduction of constructors. The \
constructor deduction will eliminate a ton of basically useless helper methods like \
make_pair, so I welcome this sugar very much. Things like the new if with \
initializers and if constexpr make C++17 just easier to write and read. Also, the new \
library has nice additions like std::optional or std::string_view, although \
array_view is missing. It has also parallel STL algorithms and the iterator hierarchy \
contains contiguous iterators, which are nice for system-programming. My favorite \
additions is std::byte. Finally we can stop to use chars as bytes.
I would really go for the latest standard, even if there are some bugs in the \
compiler or libraries. Given the expected time for a re-write or fork, there should \
be enough time to stabilize.
Cheers,
Jens
Von: zeromq-dev [mailto:zeromq-dev-bounces@lists.zeromq.org] Im Auftrag von Marcin \
Romaszewicz
Gesendet: Montag, 22. Mai 2017 20:00
An: ZeroMQ development list
Betreff: Re: [zeromq-dev] Porting libzmq to C++17
Why? C++17 is syntactic sugar on top of older versions of C++. C++17 won't give you \
more performance or better code, just easier to read. There are still lots of old \
devices which only have C++98 support, which is probably the most widely adopted C++ \
standard.
A C++17 wrapper API which is optional around the older library would be very nice for \
end users, though.
On Sun, May 21, 2017 at 3:11 AM, Bela Berde <bela.berde@gmail.com> wrote:
It is not clear to me. There are still bugs and, of course, GCC is evolving.
There should be, however, a concret action in porting zeromq to C++ 17, and at least \
on Ubuntu. Is there an initiative already put in place ?
Cheers.
Sent from my iPhone
_______________________________________________
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
[Attachment #5 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type \
content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 \
(filtered medium)"><style><!-- /* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE link=blue vlink=purple><div \
class=WordSection1><p class=MsoNormal><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi,<o:p></o:p></span></p><p \
class=MsoNormal><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p \
class=MsoNormal><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I don't \
think it is just syntactic sugar, even if the changes are not what I was hoping for. \
Inline variables and guaranteed copy elision are semantic changes, so there are some \
non-syntactic features. Most changes are small, but I think they will have \
significant impact on the way that modern C++ is written. I am thinking especially of \
structured bindings and the template deduction of constructors. The constructor \
deduction will eliminate a ton of basically useless helper methods like make_pair, so \
I welcome this sugar very much. Things like the new if with initializers and if \
constexpr make C++17 just easier to write and read. Also, the new library has nice \
additions like std::optional or std::string_view, although array_view is missing. It \
has also parallel STL algorithms and the iterator hierarchy contains contiguous \
iterators, which are nice for system-programming. My favorite additions is std::byte. \
Finally we can stop to use chars as bytes.<o:p></o:p></span></p><p \
class=MsoNormal><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p \
class=MsoNormal><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I would \
really go for the latest standard, even if there are some bugs in the compiler or \
libraries. Given the expected time for a re-write or fork, there should be enough \
time to stabilize.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p \
class=MsoNormal><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Cheers,<o:p></o:p></span></p><p \
class=MsoNormal><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Jens<o:p></o:p></span></p><p \
class=MsoNormal><span lang=EN-US \
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p \
class=MsoNormal><b><span lang=EN-US \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Von:</span></b><span \
lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> zeromq-dev \
[mailto:zeromq-dev-bounces@lists.zeromq.org] <b>Im Auftrag von </b>Marcin \
Romaszew</span><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>icz<br><b>Gesendet:</b> \
Montag, 22. Mai 2017 20:00<br><b>An:</b> ZeroMQ development list<br><b>Betreff:</b> \
Re: [zeromq-dev] Porting libzmq to C++17<o:p></o:p></span></p><p \
class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Why? C++17 is syntactic \
sugar on top of older versions of C++. C++17 won't give you more performance or \
better code, just easier to read. There are still lots of old devices which only have \
C++98 support, which is probably the most widely adopted C++ \
standard.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p \
class=MsoNormal>A C++17 wrapper API which is optional around the older library would \
be very nice for end users, though.<o:p></o:p></p></div></div><div><p \
class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Sun, May 21, 2017 at \
3:11 AM, Bela Berde <<a href="mailto:bela.berde@gmail.com" \
target="_blank">bela.berde@gmail.com</a>> wrote:<o:p></o:p></p><p \
class=MsoNormal>It is not clear to me. There are still bugs and, of course, GCC is \
evolving.<br>There should be, however, a concret action in porting zeromq to C++ 17, \
and at least on Ubuntu.<br>Is there an initiative already put in place \
?<br>Cheers.<br><br>Sent from my \
iPhone<br>_______________________________________________<br>zeromq-dev mailing \
list<br><a href="mailto:zeromq-dev@lists.zeromq.org">zeromq-dev@lists.zeromq.org</a><br><a \
href="https://lists.zeromq.org/mailman/listinfo/zeromq-dev" \
target="_blank">https://lists.zeromq.org/mailman/listinfo/zeromq-dev</a><o:p></o:p></p></div><p \
class=MsoNormal><o:p> </o:p></p></div></div></body></html>
[Attachment #6 (text/plain)]
_______________________________________________
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic