First Video: C++26: an overview - Rainer Grimm - Meeting C++ 2024
The first video from Meeting C++ 2024 has been released:
C++26: an overview - Rainer Grimm @ Meeting C++ 2024
by Rainer Grimm
Watch the video:
intermediate
Interview with Titus Winters for Meeting C++ 2024
This week Titus Winters gave an interview for Meeting C++ 2024 about his thoughts on his new role at Adobe and the wider role of C++ in Softwareengineering and its current challenges.
Interview with Titus Winters for Meeting C++ 2024
by Jens Weller & Titus Winters
Watch the video:
Speaking about C++ is tomorrow
Like in the last two years Meeting C++ is organizing an event about technical speaking at C++ conferences, aiming to help new speakers with their talks and give everyone a chance to pick up something to improve their talks! The call for talks for Meeting C++ 2024 is running until June 25th!
Speaking about C++
Organized by Jens Weller
From the event description:
This event will focus on the process of creating technical talks for the C++ community. Various speakers will share their views on how to submit, prepare and give talks to the C++ community in the form of lightning talks and a panel.
SObjectizer Tales – Epilogue--Marco Arena
The last episode of the series about SObjectizer and message passing:
SObjectizer Tales – Epilogue
by Marco Arena
From the article:
In this last episode, we conclude the series and offer suggestions for delving into more topics regarding SObjectizer.
SObjectizer Tales – 28. If I had a magic wand....--Marco Arena
A new episode of the series about SObjectizer and message passing:
SObjectizer Tales – 28. If I had a magic wand...
by Marco Arena
From the article:
In this episode I delve into what I dislike the most about the library and explore what I would change if I had a magic wand.
SObjectizer Tales – 27. Design ideas--Marco Arena
A new episode of the series about SObjectizer and message passing:
SObjectizer Tales – 27. Design ideas
by Marco Arena
From the article:
In this episode we aim to inspire new ideas and approaches to design applications using SObjectizer and its paradigm.
SObjectizer Tales – 26. Dispatcher selection--Marco Arena
A new episode of the series about SObjectizer and message passing:
SObjectizer Tales – 26. Dispatcher selection
by Marco Arena
From the article:
In this episode we explore guidelines and considerations for binding agents to dispatchers. We'll emphasize the significance of asking pertinent questions rather than expecting definitive answers, as the decision-making process hinges on the unique requirements of the system.
SObjectizer Tales – 25. Runtime telemetry--Marco Arena
A new episode of the series about SObjectizer and message passing:
SObjectizer Tales – 25. Runtime telemetry
by Marco Arena
From the article:
In this episode we learn how to get insights into application performance using SObjectizer's monitoring system.
SObjectizer Tales – 24. Delivering messages at shutdown--Marco Arena
A new episode of the series about SObjectizer and message passing:
SObjectizer Tales – 24. Delivering messages at shutdown
by Marco Arena
From the article:
In this episode we learn a feature of SObjectizer to perform arbitrary actions just before shutdown, including message delivery.
Providing a stable memory address to an external API
A post on how to provide a pointer to a Qt Model/View or other APIs storing pointers to their data without using shared_ptr or unique_ptr for the actual object.
Providing a stable memory address
by Jens Weller
From the article:
Some APIs allow you to store a pointer to your data element. This is used to access additional information from your types to display them in Model/View Architecture.
A while ago I showed how you can implement a tree with shared_ptr and enable_shared_from_this and then display this in QTreeView. And when working on my current project I knew this problem would come around again. Maybe not for a tree and a tree view, but I'll clearly need to have some way to have ui panels display and edit my data classes and store a stable memory adress as a pointer in Qt models. Back in 2015 the Qt5 example still used a pointer allocated with raw new for this, in Qt6 the example uses unique_ptr. Using shared_ptr for this back in 2015 was a good decision, and the code works very well. For the moment I don't see that my current project would need to make use of enable_shared_from_this, so using unique_ptr would be a good option...