Re: [RFC] Convert builin-mailinfo.c to use The Better String Library.
- From
David Kastrup <dak@gnu.org>
- Date
- Sep 7, 2007, 06:47 UTC
- Message-ID
- <85ejhb7yzw.fsf@lola.goethe.zz>
- In-Reply-To
- <a1bbc6950709061721r537b153eu1b0bb3c27fb7bd51@mail.gmail.com>
"Dmitry Kakurin" <dmitry.kakurin@gmail.com> writes:
Show 11 quoted lines
> On 9/6/07, Linus Torvalds <torvalds@linux-foundation.org> wrote: >> >> In other words: the choice of C is the only sane choice. I know >> Miles Bader jokingly said "to piss you off", but it's actually >> true. I've come to the conclusion that any programmer that would >> prefer the project to be in C++ over C is likely a programmer that >> I really *would* prefer to piss off, so that he doesn't come and >> screw up any project I'm involved with. > > As dinosaurs (who code exclusively in C) are becoming extinct, you > will soon find yourself alone with attitude like this.
As long as TeX, Emacs and vi are around, I would not worry too much about dinosaurs in general. But C++ is a cancerous dinosaur. It has growths that just don't belong on a C body.
Show 5 quoted lines
> I was coding in Assembly when there was no C. Then in C before C++ > was created. Now days it's C++ and C#, and I have never looked > back. Bad developers will write bad code in any language. But > penalizing good developers for this illusive reason of repealing bad > contributors is nonsense.
The problem with C++ is that every C++ developer has his own style, and reuse is an illusion within that style. Take a look at classes implementing matrix arithmetic: there are as many around as the day is long, and all of them are incompatible with one another.
With regard to programming styles, C++ does not support multiple inheritance. For a single project grown from a single start, you can get reasonable solutions. But combining stuff is creating maintenance messes.
With C, the situation is not dissimilar, but you spent less time fighting the illusion that you don't need to reimplement, anyway.
> I just wanted to get a sense of how many people share this "Git > should be in pure C" doctrine.
What nonsense. Large parts of git already are shell scripts, so obviously there is no such doctrine. Just because C++ is not a sane proposition does not mean that others might not work.
-- David Kastrup, Kriemhildstr. 15, 44793 Bochum