Date: Tue, 11 Jul 2006 00:21:19 +0200 From: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= <V.Haisman@sh.cvut.cz> To: Julian Elischer <julian@elischer.org> Cc: freebsd-hackers@freebsd.org, delphij@delphij.net, mag@intron.ac Subject: Re: kern/99979: Get Ready for Kernel Module in C++ Message-ID: <44B2D2DF.2000401@sh.cvut.cz> In-Reply-To: <44B2AE69.4080703@elischer.org> References: <200607092136.k69LaNDX055391@www.freebsd.org> <84dead720607092015q7f1701abse143f3855c2aa95a@mail.gmail.com> <1152540567.99616@origin.intron.ac> <44B2AE69.4080703@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig18E5729BA044AC2C766A8AE3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Julian Elischer wrote, On 10.7.2006 21:45: > mag@intron.ac wrote: >=20 >> 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?= >=20 > 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) Binary compatibility is always a problem, no mater the language used. Besides, doesn't the FreeBSD kernel build system always compile all modul= es? Deciding that some features are bad beforehand, before you evaluate them is IMO bad idea. Let interested people write a bunch of C++ modules with the complete language before deciding on what shouldn't be used. My $0.05... -- Vaclav Haisman --------------enig18E5729BA044AC2C766A8AE3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRLLS6ENOZDESBK8FAQIFnwgAl72K3xCG+YWMSHXUm/e5ioVrB9JRFOnq iy9LDZRd4lN8TZ9ORGxwpIyXO0nKorNutL8EOA8/i71ETPSrZyQfvHRCKpk7YHtP aw+B4Qb2MO1+x+QQH0LjXEvk3bCo7qXTbQ9QxsFqrkp/cI4BMIlDNNbqaQzVI+41 0KVzw6CEbUh8cJFT/fpwj5dvIQUTYV6RUc0Q25RuCsEnjh2JoOjq/Oq4/n7iE7x2 hAHQVkBCxP/KL3pNRU+kacFRzheFN4F0TbVg4Rp8UYY1c5xwHo5j0j9+4QWtlXFt ugx0UlsXVIGHtgO4AttO3w93e9ZYbXAmolc8u+E/+3+20XnjLl0ltg== =0bFX -----END PGP SIGNATURE----- --------------enig18E5729BA044AC2C766A8AE3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44B2D2DF.2000401>