>>40
And accidentally freeing memory that is still needed somewhere. But besides this and off-by-one errors and such there's no way a competent programmer could cause segmentation faults with manual memory management.
>>46
I guess I wanted an r/programming with less Python vs. Ruby bickering than Reddit, something in between the current subreddit and Lambda the Ultimate like /prog/was once, it seems. Maybe it's just a matter of signal to noise ratio.
On that same vein, Hacker News mostly produces high-brow sounding noise. The opinions which you find there are rarely more informed than Reddit's, lacking the contributions of actual academics and experts. It's mostly a bunch of over-serious pseudo-nerds in their twenties who want to sound like adults.
Name:
Anonymous2011-09-08 15:46
>>48 It's mostly a bunch of over-serious pseudo-nerds in their twenties who want to sound like adults.
That's the Internet, retard.
>>48
You're really not going to find that anywhere anymore, sadly. I would suggest places to you, but this board is too infested with low signal noise for me to tell you publicly.
I just saw that it bothered you. Didn't expect that. But do tell me what I'm missing. I already know that you have been here for long, longer than myself. Not that it would matter.
I think I recall some guy with your writing style some months back saying that he was trying to shitpost /prog/ into catharsis. Well, obviously that didn't work.
Name:
Anonymous2011-09-08 20:58
manual memory management increases complexity, and you blubbing assholes don't even see how.
Having some form of automatic memory management makes it so there is absolutely 0 reason not to share resources. There's no overhead whatsoever to doing things that are "bad design" in C++, and no risks either. The secret is that it's not "bad design." It's just a new technique you can do without fear of OH GOD THE MANUAL REFERENCE COUNTING SYSTEM I MADE CAN'T HANDLE CYCLES AND AH FUCK IT.
Name:
Anonymous2011-09-08 23:52
All implementations of GC are slow as hell.
Name:
Anonymous2011-09-09 5:38
RAII (Resource Acquisition Is Initialization) makes manual memory management safe and easy.
Name:
Anonymous2011-09-09 7:28
>>60
I created this thread and it seems to be going pretty well.
>>68
Not really. GC is da shit except when object lifetime can reliably be determined in advance, in which case you should use manual memory management unless you want to receive my five dollar footlong up your greasy anus.
66 is dubz in bases 10 (which itself is dubz in base 4), 21 (which itself is dubz in base 6 and tripz in base 4), and 32 (which itself is dubz in bases 7 (which itself is tripz in base 2) and 15 (which itself is dubz in base 4 and quadz in base 2))!
Name:
Anonymous2011-09-09 10:46
>>73
You just invented the science of Dubz Analysis. Congratulations, y'oure part of history now.