BTW you kill threading.
On Wed, 2005-09-07 at 11:13 +0200, Budde, Marco wrote:
[...]
> >> That would be because the kernel is written in *C* (and some asm),
> *not* C++.
>
> I cannot see the connection. At the end everything gets converted
> to assembler/opcode. In the user space I can mix C and C++ code
Yup. And exported symbols for the linker.
> without any problems, why should this not be possible in the
Yes, this is a general problem with integrated c/c++ stuff like
Win-Visual C++. People think that they can mix it freely, in fact they
are using *only* C++ (it just happens that some part of the source is
compilable with a C compiler, but since you compile everything with the
C++ compiler pressing F9, no one sees the difference).
Why do you think are all these "#ifdef _cpluplus" stuff in the header
files for?
> kernel mode?
Try linking also in the user space, not only compilation.
Second read in the standards about the difference between hosted and
standalone environments and think on the differences.
> >> There /is/ no C++ support.
>
> This will be a problem in future. Nearly nobody will start a new
No.
> larger project (driver, user space software, embedded firmware)
We re on linux-kernel@ here, so we don't care *here* for user-space
software (only for the interface - i.e. sys-calls).
And for embedded usage C++ is unsusable in user-space too since it will
ex-bloat the whole software if people simply pull-in usual and/or common
C++ libraries like the STL and use them without knowing how much object
code they explode with it (if used without thinking).
> using non OO languages today. So porting eg. Windows drivers to
Which is again wrong. You can OO software without OO languages (though
you loose some nice features and checking).
> Linux is nearly impossible without C++ support.
Is is impossible anyways since the in-kernel interfaces are probably
quite different (though I don't know anything about ).
> E.g. in my case the Windows source code has got more than 10 MB.
> Nobody will convert such an amount of code from C++ to C.
> This would take years.
First, how much of it is really the source of a kernel driver (in the
sense of a Unix/Linux kernel driver)?
And second, no one expects that you convert your driver source. Just
write it from scratch (since you know the internals of the hardware
quite well it should take only a few weeks).
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
