cqwrteur (euloanty.delete@this.live.com) on July 14, 2021 3:12 am wrote:
> > Where did you get that from? He could always ban use of the feature, or even have a ompiler
> > that didn't use debug data to restore registers - that would lead to faster predictable
> > exception handling even if it slightly slows normal processing when exceptions are not thrown.
> > It is not as though C++ actually encourages use of the feature like Python does.
>
>
> On Tue, 20 Jan 2004, Robin Rosenberg wrote:
> >
> > This is the "We've always used COBOL^H^H^H^H" argument.
>
> In fact, in Linux we did try C++ once already, back in 1992.
>
> It sucks. Trust me - writing kernel code in C++ is a BLOODY STUPID IDEA.
>
> The fact is, C++ compilers are not trustworthy. They were even worse in
> 1992, but some fundamental facts haven't changed:
>
> - the whole C++ exception handling thing is fundamentally broken. It's
> _especially_ broken for kernels.
> - any compiler or language that likes to hide things like memory
> allocations behind your back just isn't a good choice for a kernel.
> - you can write object-oriented code (useful for filesystems etc) in C,
> _without_ the crap that is C++.
>
> In general, I'd say that anybody who designs his kernel modules for C++ is
> either
> (a) looking for problems
> (b) a C++ bigot that can't see what he is writing is really just C anyway
> (c) was given an assignment in CS class to do so.
>
> Feel free to make up (d).
>
> Linus
>
>
>
> Yes, Exception Handling is the largest issue. Linus Torvalds' own words.

Yes, Linus Torvalds encouraged object-oriented code. Your turn to bite him.