I advise you to read "The Art of Unix Programming" by Eric Steven Raymond
http://www.catb.org/~esr/writings/taoup/html/ch14s04.html#cc_language
In this book you can find more about the Unix philosophy, and arguments on why 
C++ is wrong.


>----- Oorspronkelijk bericht -----
>Van: Brian Hansen [mailto:[EMAIL PROTECTED]
>Verzonden: vrijdag, december 28, 2007 07:33 AM
>Aan: misc@openbsd.org
>Onderwerp: Linus about C++
>
>Hi.
>
>This is partly not OpenBSD related, and yet again someone pointed out that
>perhaps a lot of bug could be avoided using C++. I am writting my big paper
>on C and C++ and would like some comments from people who are experts.
>
>Off-list is okay, but maybe others are interested as well.
>
>I found this statement of Linux Torvalds about C++ online:
>
><snip>
>C++ is a horrible language. It's made more horrible by the fact that a lot
>of substandard programmers use it, to the point where it's much much
>easier to generate total and utter crap with it. Quite frankly, even if
>the choice of C were to do *nothing* but keep the C++ programmers out,
>that in itself would be a huge reason to use C.
>
>C++ leads to really really bad design choices. You invariably start using
>the "nice" library features of the language like STL and Boost and other
>total and utter crap, that may "help" you program, but causes:
>
> - infinite amounts of pain when they don't work (and anybody who tells me
>   that STL and especially Boost are stable and portable is just so full
>   of BS that it's not even funny)
>
> - inefficient abstracted programming models where two years down the road
>   you notice that some abstraction wasn't very efficient, but now all
>   your code depends on all the nice object models around it, and you
>   cannot fix it without rewriting your app.
>
>In other words, the only way to do good, efficient, and system-level and
>portable C++ ends up to limit yourself to all the things that are
>basically available in C. And limiting your project to C means that people
>don't screw that up, and also means that you get a lot of programmers that
>do actually understand low-level issues and don't screw things up with any
>idiotic "object model" crap.
></snip>
>
>Is he right?
>
>Best regards, and forgive me if I am to much "off topic".

Reply via email to