Browse Source
Explicitly delete the copy constructor and copy assignment operator for FileSinkSink, which manages resources that should not be shared through implicit shallow copies. The implicitly generated copy operations could leave multiple FileSinkSink instances referring to the same resources, potentially causing invalid ownership or double deletion. Since FileSinkSink is not intended to be copied or assigned, prohibit both operations at compile time, turning potential runtime errors into compile-time errors. cppcheck identified the missing copy constructor and assignment operator with its noCopyConstructor and noOperatorEq warnings. Signed-off-by: Robin Getz <rgetz503@gmail.com>chirpmodem-v8.0.0
1 changed files with 3 additions and 1 deletions
Loading…
Reference in new issue