Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
llvm-epi-0.8
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
Roger Ferrer
llvm-epi-0.8
Commits
497d9d26
Commit
497d9d26
authored
12 years ago
by
Marshall Clow
Browse files
Options
Downloads
Patches
Plain Diff
Change C++0x references to C++11, Fixes bug #12745
llvm-svn: 167930
parent
d81108f0
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
libcxx/www/index.html
+4
-4
4 additions, 4 deletions
libcxx/www/index.html
with
4 additions
and
4 deletions
libcxx/www/index.html
+
4
−
4
View file @
497d9d26
...
@@ -57,7 +57,7 @@
...
@@ -57,7 +57,7 @@
</ul>
</ul>
<!--=====================================================================-->
<!--=====================================================================-->
<h2
id=
"why"
>
Why a new C++ Standard Library for C++
'0x
?
</h2>
<h2
id=
"why"
>
Why a new C++ Standard Library for C++
11
?
</h2>
<!--=====================================================================-->
<!--=====================================================================-->
<p>
After its initial introduction, many people have asked "why start a new
<p>
After its initial introduction, many people have asked "why start a new
...
@@ -72,14 +72,14 @@
...
@@ -72,14 +72,14 @@
to how they are implemented. For example, it is generally accepted that
to how they are implemented. For example, it is generally accepted that
building std::string using the "short string optimization" instead of
building std::string using the "short string optimization" instead of
using Copy On Write (COW) is a superior approach for multicore
using Copy On Write (COW) is a superior approach for multicore
machines (particularly in C++
'0x
, which has rvalue references). Breaking
machines (particularly in C++
11
, which has rvalue references). Breaking
ABI compatibility with old versions of the library was
ABI compatibility with old versions of the library was
determined to be critical to achieving the performance goals of
determined to be critical to achieving the performance goals of
libc++.
</p></li>
libc++.
</p></li>
<li><p>
Mainline libstdc++ has switched to GPL3, a license which the developers
<li><p>
Mainline libstdc++ has switched to GPL3, a license which the developers
of libc++ cannot use. libstdc++ 4.2 (the last GPL2 version) could be
of libc++ cannot use. libstdc++ 4.2 (the last GPL2 version) could be
independently extended to support C++
'0x
, but this would be a fork of the
independently extended to support C++
11
, but this would be a fork of the
codebase (which is often seen as worse for a project than starting a new
codebase (which is often seen as worse for a project than starting a new
independent one). Another problem with libstdc++ is that it is tightly
independent one). Another problem with libstdc++ is that it is tightly
integrated with G++ development, tending to be tied fairly closely to the
integrated with G++ development, tending to be tied fairly closely to the
...
@@ -87,7 +87,7 @@
...
@@ -87,7 +87,7 @@
</li>
</li>
<li><p>
STLport and the Apache libstdcxx library are two other popular
<li><p>
STLport and the Apache libstdcxx library are two other popular
candidates, but both lack C++
'0x
support. Our experience (and the
candidates, but both lack C++
11
support. Our experience (and the
experience of libstdc++ developers) is that adding support for C++11 (in
experience of libstdc++ developers) is that adding support for C++11 (in
particular rvalue references and move-only types) requires changes to
particular rvalue references and move-only types) requires changes to
almost every class and function, essentially amounting to a rewrite.
almost every class and function, essentially amounting to a rewrite.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment