OK, let's get a couple of things clear...
No one here "hates" C++ per se. It is a tool, and every tool has its purpose.
Using C++ in the kernel has not been deemed apropriate for several
reasons. There are several (other) reasons to make the Linux Kernel C
only, this has been discussed, trolled, flamed, argued, come, gone,
etc, etc FAQs and searches are your friend there.
In your scenario, you have two possible option (IMHO)
1 - Port your existing code to C
2- keep it in C++, keep it in user level and have a simple file system
driver communicating with your existing code (I think FUSE applies to
the situation)
Thiago
On 4/24/06, Gary Poppitz <[email protected]> wrote:
> > We know they are "incompatible", why else would we allow "private" and
> > "struct class" in the kernel source if we some how expected it to work
> > with a C++ compiler?
>
>
> I can see that this was intentional, not an oversight.
>
> If there is a childish temper tantrum mentality about C++ then I have
> no reason or desire to be on this list.
>
> Grow up.
> -
> 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/
>
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
