From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 10 19:45:50 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2798516A4E2 for ; Mon, 10 Jul 2006 19:45:50 +0000 (UTC) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE0B843D73 for ; Mon, 10 Jul 2006 19:45:46 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.18.229]) ([10.251.18.229]) by a50.ironport.com with ESMTP; 10 Jul 2006 12:45:46 -0700 Message-ID: <44B2AE69.4080703@elischer.org> Date: Mon, 10 Jul 2006 12:45:45 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mag@intron.ac References: <200607092136.k69LaNDX055391@www.freebsd.org> <84dead720607092015q7f1701abse143f3855c2aa95a@mail.gmail.com> <1152540567.99616@origin.intron.ac> In-Reply-To: <1152540567.99616@origin.intron.ac> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, delphij@delphij.net Subject: Re: kern/99979: Get Ready for Kernel Module in C++ X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 19:45:50 -0000 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"