On Tue, 15 Oct 2002, Daniele Lugli wrote:
> But let me at least summarize my poor-programmer-not-kernel-developer
> point of view: at present the kernel if a mined field for c++ and i
> understand it is not viable nor interesting for the majority to rewrite
> it in a more c++-friendly way. But why not at least keep in mind, while
> writing new stuff (not the case of current.h i see), that kernel headers
> could be included by c++?
current.h is, indeed, a special case. #define i j would not be tolerated
simply because it's stupid. Abuses of preprocessor are generally frowned
upon, but there are passionate wa^H^Hpersons who just can't help themselves
and use e.g. ## for no good reason.
But as for C++... frankly, for all I care it doesn't exist. As long as
requirements of style happen to reduce problems of C++ programmers -
they are lucky. But other than that... watch me not care. In the linux
kernel context C++ is obscure language and it will stay that way. Ergo,
no reasons to spend any mental efforts on being nice to it. Deal.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Oct 15 2002 - 22:00:57 EST