So is Ruby! And it is still possible to write bad code with either of them.<br><br><br><b><i>jim stockford <firstname.lastname@example.org></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> <br>yes! objective C is clean and good!<br><br>On Jul 11, 2006, at 9:39 AM, Rick Moen wrote:<br><br>> Quoting jim stockford (email@example.com):<br>><br>>> The promise that once debugged, underlying class code<br>>> need not be re-debugged as one develops classes turned<br>>> out to be sometimes mistaken.<br>>> For MSFT Visual C++ at least, the virtual table mechanism<br>>> allows occasional corruption of resources.<br>>> Multiple inheritance is scary on the face of it, at least to me.<br>>> Pointedly, the remark is about the risks of the underlying<br>>> classes' behavior, not code readability or the skill of any<br>>> particular
programmer.<br>><br>> My wife likes to say that inheritance means you can inherit bugs (too).<br>><br>> The thing about C++ is that (along with Java) it's about the worst<br>> possible advertisement for OO programming (in my view), and I never <br>> much<br>> liked that language category until I encountered better examples. In<br>> particular, it's a darned shame that Ojective C never caught on instead<br>> of C++; the world would be a much better place.<br>><br>><br>> _______________________________________________<br>> sf-lug mailing list<br>> firstname.lastname@example.org<br>> http://linuxmafia.com/mailman/listinfo/sf-lug<br>><br><br><br>_______________________________________________<br>sf-lug mailing list<br>email@example.com<br>http://linuxmafia.com/mailman/listinfo/sf-lug<br></blockquote><br><p>
<hr size=1>Yahoo! Music Unlimited - Access over 1 million songs.
">Try it free.</a>