Date: Mon, 10 Jul 2006 12:45:45 -0700 From: Julian Elischer <julian@elischer.org> To: mag@intron.ac Cc: freebsd-hackers@freebsd.org, delphij@delphij.net Subject: Re: kern/99979: Get Ready for Kernel Module in C++ Message-ID: <44B2AE69.4080703@elischer.org> In-Reply-To: <1152540567.99616@origin.intron.ac> References: <200607092136.k69LaNDX055391@www.freebsd.org> <84dead720607092015q7f1701abse143f3855c2aa95a@mail.gmail.com> <1152540567.99616@origin.intron.ac>
next in thread | previous in thread | raw e-mail | index | archive | help
mag@intron.ac wrote: > Joseph Koshy wrote: > >> >>> I would write my kernel module in C++, just like IOKit >>> of OpenDarwin. Thus, all conflicts against C++ in current >>> FreeBSD kernel source must be swept out firstly. >> >> While the idea of using C++ in the kernel made me very nervous, I have seen some places where an official subset might be useful. is it worth having a discussion about what features of C++ (or modular C) we would want to support and what would remain "illegal" in the kernel? Inherritance would be noce but there are traps.. e.g. How do you cope with classes depending on superclasses that may be from a different module and may have been compiled at a different time? (i.e. the base structure may have changed) > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44B2AE69.4080703>