←back to thread

327 points AareyBaba | 1 comments | | HN request time: 0.001s | source
Show context
mwkaufma ◴[] No.46183728[source]
TL;DR

- no exceptions

- no recursion

- no malloc()/free() in the inner-loop

replies(9): >>46183820 #>>46183900 #>>46184073 #>>46184113 #>>46184198 #>>46184398 #>>46184472 #>>46184588 #>>46185500 #
jandrewrogers ◴[] No.46183820[source]
i.e. standard practice for every C++ code base I've ever worked on
replies(1): >>46183866 #
DashAnimal ◴[] No.46183866[source]
What industry do you work in? Modern RAII practices are pretty prevalent
replies(2): >>46183904 #>>46184092 #
jandrewrogers ◴[] No.46183904[source]
What does RAII have to do with any of the above?
replies(4): >>46183995 #>>46184069 #>>46184097 #>>46184150 #
WD-42 ◴[] No.46183995[source]
0 allocations after the program initializes.
replies(4): >>46184066 #>>46184067 #>>46184129 #>>46184331 #
Gupie ◴[] No.46184067[source]
Open a file in the constructor, close it in the destructor. RAII with 0 allocations.
replies(1): >>46187701 #
dh2022 ◴[] No.46187701[source]
std::vector<int> allocated and freed on the stack will allocate an array for its int’s on the heap…
replies(2): >>46189144 #>>46193524 #
1. Gupie ◴[] No.46193524{3}[source]
Sure, but my point was that RAII doesn't need to involve the heap. Another example would be acquiring abd releasing a mutex.