Skip to main content

Timeline for Linked list, pointer practice

Current License: CC BY-SA 3.0

11 events
when toggle format what by license comment
May 23, 2017 at 12:41 history edited CommunityBot
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Mar 9, 2017 at 21:45 comment added Edward @LokiAstari Perhaps I should have phrased it as "prefer smart pointers to raw pointers" rather than "avoid using pointers." As you rightly point out, using pointers judiciously is still a handy and valuable technique.
Mar 9, 2017 at 21:32 comment added Loki Astari I disagree with the comment on pointers. Yes modern code should definitely prefer smart pointers or other tools over old RAW pointers. But there are certain situations where pointers are acceptable (as long as they don't leak out of your class and you just use them internally). Building containers is one such situation.
Mar 9, 2017 at 19:42 comment added Charles @Edward Thank you so much! I have bunch more questions now and wasn't sure how to get them in here without adding them to the original question. Thanks again in advance for any further expertise you provide!
Mar 9, 2017 at 19:27 vote accept Charles
Mar 9, 2017 at 16:51 history edited Edward CC BY-SA 3.0
fixed bug
Mar 9, 2017 at 16:40 history edited Edward CC BY-SA 3.0
removed spurious diagnostic line
Mar 9, 2017 at 16:34 comment added Edward @Rakete1111 You're right. I've corrected my answer. Thanks!
Mar 9, 2017 at 16:34 history edited Edward CC BY-SA 3.0
added correction per Rakete1111
Mar 9, 2017 at 16:28 comment added Rakete1111 "This means that any calling code could arbitrarily set that to some other value, like nullptr" Nope, the calling code can only modify the instance pointed by the pointer, but not the pointer itself, as it is passed by value and not by reference
Mar 9, 2017 at 13:20 history answered Edward CC BY-SA 3.0