Timeline for Doubly linked std::list simple implementation
Current License: CC BY-SA 3.0
16 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 24, 2017 at 3:06 | review | Close votes | |||
Mar 24, 2017 at 9:20 | |||||
Mar 19, 2017 at 19:39 | vote | accept | Alexander | ||
Mar 19, 2017 at 19:39 | vote | accept | Alexander | ||
Mar 19, 2017 at 19:39 | |||||
Mar 19, 2017 at 12:41 | answer | added | Loki Astari | timeline score: 3 | |
Mar 18, 2017 at 20:36 | comment | added | Incomputable |
@Alexander, pop_xxx need to delete as well, otherwise you're leaking memory. When you assign nullptr to non deleted chunk of memory, you're basically saying "lets waste memory". I believe I gave enough information, good luck.
|
|
Mar 18, 2017 at 20:32 | comment | added | Incomputable |
@Alexander, C++ doesn't have garbage collection. Assigning nullptr won't release the memory. You need to call delete. Current code looks like freelist, not a list.
|
|
Mar 18, 2017 at 20:30 | history | edited | Alexander | CC BY-SA 3.0 |
added 165 characters in body
|
Mar 18, 2017 at 18:32 | comment | added | Deduplicator |
every case, just like pop_back()
|
|
Mar 18, 2017 at 16:57 | comment | added | πάντα ῥεῖ | @Alexander In fact I think there are more than one possible cases your code is prone for leaking, hence I proposed using smart pointers. | |
Mar 18, 2017 at 16:53 | history | edited | Jamal | CC BY-SA 3.0 |
deleted 4 characters in body; edited title
|
Mar 18, 2017 at 15:49 | comment | added | Deduplicator |
pop_front() leaks.
|
|
Mar 18, 2017 at 15:26 | answer | added | πάντα ῥεῖ | timeline score: 3 | |
Mar 18, 2017 at 14:12 | history | edited | Alexander | CC BY-SA 3.0 |
deleted 3 characters in body
|
Mar 18, 2017 at 13:49 | review | Close votes | |||
Mar 19, 2017 at 11:50 | |||||
Mar 18, 2017 at 13:34 | review | First posts | |||
Mar 18, 2017 at 13:36 | |||||
Mar 18, 2017 at 13:26 | history | asked | Alexander | CC BY-SA 3.0 |