drath/linuxSmartie
0
0
Fork 0
Code Issues Pull Requests Actions Projects Releases Wiki Activity

make the scoping thing clearer

Browse Source
This commit is contained in:
drath
2025-10-01 22:59:39 +02:00
parent 9a769aec27
commit aa75aa2b30
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
main.cpp
View File

@@ -41,7 +41,7 @@ struct Sensors {
std::mutex mtx; // making sure the struct isnt accessed by multiple threads at once std::mutex mtx; // making sure the struct isnt accessed by multiple threads at once
}; };
void sighandler(int s) { void sighandler(int s) { // can i remove int s
std::println("[Signal] got SIGINT/SIGTERM, exiting..."); std::println("[Signal] got SIGINT/SIGTERM, exiting...");
sem::main.release(); sem::main.release();
sem::display.release(); sem::display.release();
@@ -147,8 +147,8 @@ int main(int argc, char* argv[]) {
/* what the fucking kind of code is this /* what the fucking kind of code is this
this code below spins up display/sensors/homeassistant functions as threads and halts until sem::main is released in sighandler this code below spins up display/sensors/homeassistant functions as threads and halts until sem::main is released in sighandler
its scoped because when sem::main is released, program destroys the std::jthreads and the vector before leaving the scope then the program leaves the scope, but before that, it destroys the std::jthreads in the "threads" vector
this causes all threads to join back into main thread before leaving the scope, so we can safely destroy pSensors without segfault this causes all threads to gracefully close and join back into main thread, so we can safely destroy pSensors without segfault
*/ */
{ {