[lkml]   [2000]   [Oct]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Criticism] On the discussion about C++ modules

The [new] and constructor/destructor operations create hidden memory
allocations in C++ that can blow performance in kernel "fast paths".
Writing kernel code in C++ is never a good idea because of this problem,
and the fact that with function overloading, it's possible for someone
to write code that is so difficult to follow, it's unmaintainable. MS
wrote a large portion of W2K in C++, which is one reason it's hard to
debug, and slow. C++ also puts in jump tables with mangled names, and
is very difficult to debug at the assembler level.

C++ is very good for application programmers who reuse a lot of code
because it allows the creation of building block libraries -- it's not
good for kernel development, IMHO where speed and supportability is more
important that modularity....

I think that perhaps in the beginning C and C++ were not languages --
they were grades (snicker, snicker).


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:41    [W:0.175 / U:1.452 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site