Keynote: Safety, Security, Safety[sic] and C/C++[sic] - C++ Evolution - Herb Sutter - ACCU 2024
ฝัง
- เผยแพร่เมื่อ 15 มิ.ย. 2024
- ACCU Membership: tinyurl.com/ydnfkcyn
---
Keynote: Safety, Security, Safety[sic] and C/C++[sic] - C++ Evolution - Herb Sutter - ACCU 2024
---
As the world’s threats and dangers evolve, so too must our tools. Sometimes a tool can evolve sufficiently to be useful in a new environment. Other times, a tool has to be used less or exchanged for a different one.
This talk addresses several questions:
- Why does the title say “safety” twice?
- Why is “C/C++” an essential term to embrace, not avoid?
- Is distinguishing “C vs C++” a True Scotsman problem?
- What is recognizably “C++” as C++ continues to evolve?
- Why hope for major improvement in C, C++, and C/C++?
Finally, the talk will also cover a few other updates about other C++ evolution (including reflection!) and from my personal ongoing experiment with my cppfront compiler.
Slides: accu.org/conf-previous/accu2024/
Sponsored By think-cell
---
Herb Sutter
Author, chair of the ISO C++ committee, software architect at Microsoft.
---
The ACCU Conference is the annual conference of the ACCU membership, but is open to any and all who wish to attend. The tagline for the ACCU is 'Professionalism in Programming', which captures the whole spectrum of programming languages, tools, techniques and processes involved in advancing our craft. While there remains a core of C and C++ - with many members participating in respective ISO standards bodies - the conference, like the organisation, embraces other language ecosystems and you should expect to see sessions on C#, D, F#, Go, Javascript, Haskell, Java, Kotlin, Lisp, Python, Ruby, Rust, Swift and more.The ACCU Conference is a conference by programmers for programmers about programming.
Discounted rates for members.
ACCU Membership: tinyurl.com/ydnfkcyn
2024 Program: accu.org/conf-previous/accu2024/
accu.org
www.accuconference.org/
mastodon.social/@ACCUConf
/ accu-conference
bsky.app/profile/accuconf.bsk...
/ accuorg
/ accuconf
---
TH-cam Videos Filmed, Edited & Optimised by Digital Medium: events.digital-medium.co.uk
#accuconf #programming #cplusplus #cpp #cprogramming - วิทยาศาสตร์และเทคโนโลยี
Circle is without a doubt the most promising development for C++. Too many people unfortunately can't set their egos aside to give it the attention it really deserves.
just adopt Circle as c++2x
This talk is highly interesting, very good points
Really enjoyed this Herb, thank you!
Great talk as always!
Question: With so many copyright holders, will you be able to change the license of Cppfront to a free license?
I believe the license is creative-commons
@@RoibarkanYes, but using NC (non-commercial) and ND (no derivations). This means cppfront can’t be included by default in any GNU/Linux-distribution, no company can use it and those contributors Herb celebrates are technically not even allowed to provide pull requests since that involves modifying the sources.
Because of that it is hard to take cppfront seriously until Herb switches to a free license.
16:15 JF Bastien’s talk from CppNow 2023: th-cam.com/video/Gh79wcGJdTg/w-d-xo.html
Rust is imperfect. However, rewriting in Rust provides a direct path to safety. If performance is still an issue, rewrite in Verilog.
When has Stroustrup ever agreed to break backwards compatibility in the name of basic safety or security guarantees? He doesn't even support a builtin package manager. Rather than wait a century for reasonably high quality defaults, adopt a modern systems language. Even Go can do the job for the vast majority of applications.
one big question is, why is C++ default regexp so slow compared to perl ?...
From what I've heard the limitations are caused by abi backwards compatibility.
The reason, that I know and is mostly cited in the community, is that they did some "bad" decisions in the implementation but now they can't change it because this will be ABI breakage.
ABI issues.
how is that relevant to this talk?
I don’t understand why it is impossible to fix. Why can’t they wrap the old and the new data structures in a union and stay abi compatible?