On Thu, 27 Apr 2000, Manfred Spraul wrote:
> Alexander Viro wrote:
> >
> > <shrug> basically, I couldn't care less for C++ - it has no business
> > seeing the internal kernel stuff and that's what __KERNEL__ is for.
> >
> Why not?
>
> Someone might try to port a device driver that was written in C++ from
> another OS to Linux, and then this would be a problem.
>
> We should not use "new" and "virtual" as variable names, and perhaps we
> should also add ".o.cpp" to Rules.mak and mkdep.
>
> We don't need to support RTTI or exception handling, but IMHO we should
> not deliberately prevent C++ device drivers from compiling.
<shrug> differences between the code disciplines to be used in drivers
for different systems are _much_ larger than the difference between C++
and C. Again, I'm not on a holy crusade against C++. If somebody wants to
write in INTERCAL, BLISS, MACRO-10 with appropriate set of macros, Alef,
PASCAL or Ada - fine, it's Not My Problem(tm). Ditto for other weird
languages. C++ is no different in that respect. You choose the langauge,
you do whatever you need to compile your code and keep it working. I don't
care and I don't want to care.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 30 2000 - 21:00:16 EST