2 ms·
I'm not necessarily saying the features omitted from C++ were omitted for "good and sufficient" reasons, and I certainly didn't say they were a bad idea. What I
by scott_s 17y ago
I'm not necessarily saying the features omitted from C++ were omitted for "good and sufficient" reasons, and I certainly didn't say they were a bad idea. What I am saying is they were omitted for reasons other than the author states. (The reason I'm not saying they are good and sufficient is that starts a discussion about the design of C++, which I think is too far off topic.)
I can't speak with confidence about Ruby's culture. But the talk I've seen about not freely modifying arbitrary classes seems to run counter with the author's main point, since that is the sort of freedom he's talking about. That sort of proscription reminds me of warnings against global state in procedural programs, and shared state in parallel programs.