4 ms·
Section 10.7 of "The Design and Evolution of C++" has some good ones from the early 90s: "When (not if) garbage collection becomes available, we will have two
by jlarocco 3y ago
Section 10.7 of "The Design and Evolution of C++" has some good ones from the early 90s:
"When (not if) garbage collection becomes available, we will have two ways of writing C++ programs."
"I suspect that a garbage collection scheme can be concocted that will work with (almost) every legal C++ program, but work even better when no unsafe operations are used."
"I am under no illusion that building an acceptable garbage collection mechanism for C++ will be easy - I just don't think it is impossible. Consequently, given the number of people looking at the problem several solutions will soon emerge."
- fluoridation 3y agoWell, we now have garbage collection. Just not tracing garbage collection.
- pjmlp 3y agoTracing GC is there on C++/CLI, Unreal C++, Bohem and V8's Olipan.
- fluoridation 3y agoBut not on standard C++. And C++/CLI doesn't collect garbage of native objects.
- pjmlp 3y agoDepends on how C++/CLI was compiled, and how was that allocation done. TIMTOWTDI The biggest issue with current ISO C++ is that the standard desigs some features on paper, instead of adopting existing extensions as standard features, as it used to be. Hence when paper designed features get wrongly designed, no one picks them up.
- einpoklum 3y agoActually, these quotes have become outdated by the language itself! ... in favor of this quote: > I don't like garbage. I don't like littering. My ideal is to eliminate the need for a garbage collector by not producing any garbage. That is now possible. See this question: https://stackoverflow.com/q/147130/1593077 https://stackoverflow.com/q/147130/1593077 and this answer (of mine): https://stackoverflow.com/a/48046118/1593077 https://stackoverflow.com/a/48046118/1593077
- froh 3y agofor cyclic object graphs you build your own GC, no matter if you call it such, or you leak memory.