木头云 91e4489a55 refactor(buffer): rename 'additional' parameter to 'mem_to_free' for clarity ... Header changes (include/libipc/buffer.h): - Rename: additional → mem_to_free (better semantic name) - Add documentation comments explaining the parameter's purpose - Clarifies that mem_to_free is passed to destructor instead of p - Use case: when data pointer is offset into a larger allocation Implementation changes (src/libipc/buffer.cpp): - Update parameter name in constructor implementation - No logic changes, just naming improvement Test changes (test/test_buffer.cpp): - Fix TEST_F(BufferTest, ConstructorWithMemToFree) - Previous test caused crash: passed stack variable address to destructor - New test correctly demonstrates the parameter's purpose: * Allocate 100-byte block * Use offset portion (bytes 25-75) as data * Destructor receives original block pointer for proper cleanup - Prevents double-free and invalid free errors Semantic explanation: buffer(data_ptr, size, destructor, mem_to_free) On destruction: destructor(mem_to_free ? mem_to_free : data_ptr, size) This allows: char* block = new char[100]; char* data = block + 25; buffer buf(data, 50, my_free, block); // Frees 'block', not 'data'		2025-11-30 05:09:56 +00:00
..
libipc	refactor(buffer): rename 'additional' parameter to 'mem_to_free' for clarity	2025-11-30 05:09:56 +00:00