From owner-freebsd-questions Fri Aug 11 19:48:59 2000 Delivered-To: freebsd-questions@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id BFADB37B51F for ; Fri, 11 Aug 2000 19:48:52 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 13NPgp-000Ixn-00; Sat, 12 Aug 2000 02:02:19 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 13NPgr-000F8p-00; Sat, 12 Aug 2000 02:02:21 +0100 Date: Sat, 12 Aug 2000 02:02:21 +0100 From: Ben Smithurst To: Isaac Waldron Cc: freebsd-questions@freebsd.org Subject: Re: C++ comments in kernel module Message-ID: <20000812020221.P48327@strontium.scientia.demon.co.uk> References: <200008111501.LAA00387@waldron.house> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200008111501.LAA00387@waldron.house> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Isaac Waldron wrote: > I am working on a kernel module for the plex86 vm project, and have run into a > small issue with some of the non-OS specific code. This code has C++ style > '//' comments in it, which are disallowed by gcc when the -ansi flag is used. > Does anyone know of a way to re-enable these comments, and if not, is there > any harm in disabling the -ansi flag when compiling a kernel module? Just don't use those comments, use real C /* comments */ instead. I think technically the // comments are legal ANSI C now, but haven't been for long and I guess the compilers haven't caught up yet. But no, I don't think removing -ansi will hurt. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D FreeBSD Documentation Project / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message