Leveraging C++20/23 Features for Low Level Interactions - Jeffrey Erickson - CppCon 2024

preview_player
Показать описание
---

Leveraging C++20/23 Features for Low Level Interactions - Jeffrey Erickson - CppCon 2024
---

Low level interactions are a core part of embedded implementations. All too often, C++ developers rely on C constructs and interactions due to prior biases around language support. Herein we present effective leveraging of C++20 and C++23 constructs in an embedded driver code base. From using an existing C driver more effectively with modern C++ smart pointers to leveraging constexprs for bit and byte manipulation in the standard library, we will go over how you can stay on the cutting edge of the C++ language evolution in the embedded space.
---

---

Jeffrey Erickson

Jeffrey E Erickson works in HW/SW Codesign Architecture at Altera, an Intel company. He holds a BS in Electrical and Computer Engineering from the University of Virginia and a doctorate from Rutgers University and UMDNJ. For 15 years he has worked in embedded systems development including FPGA-processor integration, secure firmware development, and systems modeling. He holds 3 patents in image processing and signal integrity.
---

CppCon is the annual, week-long face-to-face gathering for the entire C++ community. The conference is organized by the C++ community for the community. You will enjoy inspirational talks and a friendly atmosphere designed to help attendees learn from each other, meet interesting people, and generally have a stimulating experience. Taking place this year in Aurora, Colorado, near the Denver airport, and including multiple diverse tracks, the conference will appeal to anyone from C++ novices to experts.
---

---

#cpp #cplusplus #cppcon #cppprogramming #cplusplusprogramming #softwaredevelopment #softwareengineering #coding #code #computerscience #technology #technews #programming #programmer
Рекомендации по теме
Комментарии
Автор

7:13 - well, the get() will return the pointer by value, so the next call to it will return the same pointer by value. Of course the my_c_api() can change the data pointed by that pointer. But it can't change the pointer stored inside the smart pointer via the get() --> because it gets that as a copy.

The my_c_api() can still delete the pointed memory though leading to disaster.

opokatech
Автор

44:02 alignas(4) ? before each field in the data structure, will manage individual field alignment for small padding amounts with items of different sizes

DM-fwsu
Автор

There are a lot of things wrong. The speaker talks about unique pointer but i would use reference because the base address is static

TheNovakon
Автор

C++26 Standards Committee:"Use c++, but don't negate it's advantages by creating dangerous c-like code..."

NSA:"Please use Rust, but don't negate its advantages by creating dangerous c++ -like code..."

abdulshabazz
Автор

Isn't the use of volatile discouraged?

raymundhofmann
Автор

3:56 "Question"? Wow I can't believe it. Please remove this video and ban this guy asap🤣

master