From 18aece04d5d3c3dde33fb3fa63842677d2c60bf3 Mon Sep 17 00:00:00 2001 From: Stanislav Angelovic Date: Sat, 30 Dec 2023 19:47:08 +0100 Subject: [PATCH] chore: remove legacy comments --- src/Proxy.h | 23 ----------------------- 1 file changed, 23 deletions(-) diff --git a/src/Proxy.h b/src/Proxy.h index 810f641..99254d5 100644 --- a/src/Proxy.h +++ b/src/Proxy.h @@ -94,29 +94,6 @@ namespace sdbus::internal { Slot slot; }; -// using InterfaceName = std::string; -// struct InterfaceData -// { -// using SignalName = std::string; -// struct SignalData -// { -// SignalData(Proxy& proxy, signal_handler callback, Slot slot) -// : proxy(proxy) -// , callback(std::move(callback)) -// , slot(std::move(slot)) -// {} -// Proxy& proxy; -// signal_handler callback; -// // slot must be listed after callback to ensure that slot is destructed first. -// // Destructing the slot will sd_bus_slot_unref() the callback. -// // Only after sd_bus_slot_unref(), we can safely delete the callback. The bus mutex (SdBus::sdbusMutex_) -// // ensures that sd_bus_slot_unref() and the callback execute sequentially. -// Slot slot; -// }; -// std::map> signals_; -// }; -// std::map interfaces_; - // We need to keep track of pending async calls. When the proxy is being destructed, we must // remove all slots of these pending calls, otherwise in case when the connection outlives // the proxy, we might get async reply handlers invoked for pending async calls after the proxy