From: Csaba Raduly <rcsaba@gmail.com>
To: cygwin list <cygwin@cygwin.com>
Subject: Re: Why does -std=c++11 hide certain function calls
Date: Thu, 06 Sep 2018 09:18:00 -0000 [thread overview]
Message-ID: <CAEhDDbBXkc-8t3qZ5fK0O6=FZ4kwFJ-SHbUs9wC5hBYENAyKMQ@mail.gmail.com> (raw)
In-Reply-To: <CAJn6YFDfNZdr=r+MbNQcRsPyEf8K0-=SXN13Qt5p-m9t=u24Bw@mail.gmail.com>
Hi John,
On Thu, Sep 6, 2018 at 8:45 AM, John Selbie wrote:
> Ahhhh…. that was my mistake. I had erroneously assumed that not specifying
> -std would result in the oldest version of C++.
This depends on the compiler. For a long time, the default C++ dialect
used by both GCC and clang was C++98.
Since GCC 6.0 and clang 6.0.0, the default C++ dialect is now C++14
https://gcc.gnu.org/gcc-6/changes.html
https://isocpp.org/blog/2018/03/clang-6.0.0-released
Csaba
--
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformat way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-09-06 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 5:56 John Selbie
2018-09-05 18:46 ` Hans-Bernhard Bröker
2018-09-05 19:36 ` John Selbie
2018-09-05 20:41 ` Brian Inglis
2018-09-06 0:14 ` Doug Henderson
2018-09-06 6:45 ` John Selbie
2018-09-06 9:18 ` Csaba Raduly [this message]
2018-09-06 14:07 ` Jeffrey Walton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEhDDbBXkc-8t3qZ5fK0O6=FZ4kwFJ-SHbUs9wC5hBYENAyKMQ@mail.gmail.com' \
--to=rcsaba@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).