From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751237AbWDXUaX (ORCPT ); Mon, 24 Apr 2006 16:30:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751239AbWDXUaW (ORCPT ); Mon, 24 Apr 2006 16:30:22 -0400 Received: from iabervon.org ([66.92.72.58]:27664 "EHLO iabervon.org") by vger.kernel.org with ESMTP id S1751237AbWDXUaV (ORCPT ); Mon, 24 Apr 2006 16:30:21 -0400 Date: Mon, 24 Apr 2006 16:30:36 -0400 (EDT) From: Daniel Barkalow To: Gary Poppitz cc: linux-kernel@vger.kernel.org Subject: Re: Compiling C++ modules In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 24 Apr 2006, Gary Poppitz wrote: > I have the task of porting an existing file system to Linux. This code is in > C++ and I have noticed that the Linux kernel has > made use of C++ keywords and other things that make it incompatible. You probably want to look into FUSE. C++ isn't going to be supported in the kernel, for a variety of reasons, but filesystems don't have to be in the kernel these days. FUSE seems to have C++ bindings with templates and stuff, too, so it should be an easy task. -Daniel *This .sig left intentionally blank*