Charles Levert wrote:
>
> The Linux Kernel Mailing List FAQ already addresses C vs C++. Linux
> and Plex86 are two, but then again, both are system programming.
> Reading that part of the FAQ is instructive in the context of this
> discussion.
>
> http://www.tux.org/lkml/index.html#s1-4
I added an entry in the FAQ, that C is the language to program
all new plex86 code. I also added this URL.
Not only do I fully agree with the decision to keep the Linux kernel
in C, but it is important that we keep at least certain parts of our
virtualization in C, too to be compatible with the Linux kernel and
other C-based kernels. This is because, for purposes of improving
performance, it is quite conceivable we may move parts of certain
functionality into monitor space. This will prevent the long distance
context switches back to user space and then back again to the monitor.
The C++ plugin code that we have, is OK for now as it has accelerated
the coding progress (bochs + write-cache). But from now on, all
new code should be in C, for the above reasons.
To be stated another way, no new C++ code is going to be committed
to CVS. Thus further discussions would be futile.
-Kevin
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Kevin Lawton [EMAIL PROTECTED]
MandrakeSoft, Inc. Plex86 developer
http://www.linux-mandrake.com/ http://www.plex86.org/
