Re:Libcu++: Nvidia C++ Standard Library
by quotemstr on Saturday September 19, 2020 @01:39PM
(#24529128)
There should be no expectation of C++ ABI compatibility. Do you want your system to be ABI compatible or do you want it to evolve? You can't have both. You have to pick one. I favor evolution.
[ Parent
| on HN ]
Re:Libcu++: Nvidia C++ Standard Library
by retrac on Saturday September 19, 2020 @03:35PM
(#24529878)
A properly designed ABI is capable of expansion. The design risk is not so much being backed into a corner, as just accumulating a great deal of obsolete cruft over the years/decades.
Win32 is a great example of this. It has been extensively overhauled, and best practice for writing a new application today is quite different from 25 years ago, but unmodified Windows 95 applications still usually run correctly.
Re:Libcu++: Nvidia C++ Standard Library
by quotemstr on Saturday September 19, 2020 @09:41PM
(#24531410)
The C++ standard library is a bit different from a platform API. The C++ standard library is a template system designed to conform exactly to your particular program. It should always be statically linked. I see zero advantage to dynamic linking of libc++. A platform API, on the other hand, is designed to stable, safe, and flexible, not fast --- because programs in general shouldn't be calling into the system so much. The performance costs we accept in a platform API (e.g., user to kernel privilege transition) would be totally unacceptable as part of an STL data structures implementation.
Except when OSes happen to be written in C++, like most modern non-UNIX/POSIX clones, and security updates come into play.