From owner-freebsd-stable Fri Jul 7 7:57:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id BF27E37C597 for ; Fri, 7 Jul 2000 07:57:01 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e67EtkU14564; Fri, 7 Jul 2000 07:55:46 -0700 (PDT) Date: Fri, 7 Jul 2000 07:55:46 -0700 From: Alfred Perlstein To: Graham Wheeler Cc: Jim King , Thomas David Rivers , freebsd-stable@FreeBSD.ORG Subject: Re: Any chance of changing struct member names in nameser.h? Message-ID: <20000707075545.E25571@fw.wintelcom.net> References: <200007071320.JAA86645@lakes.dignus.com> <003d01bfe81e$553eb8a0$a44b8486@jking> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from gram@cequrux.com on Fri, Jul 07, 2000 at 04:31:51PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Graham Wheeler [000707 07:46] wrote: > Jim King wrote: > > > > In that case, although it's considerably more work I'd take a look at > > writing some C wrappers around the offending stuff. You could write the > > wrappers such that they'd compile with the offending include file, and be > > callable from C++. Sounds tedious and time consuming, but it might be > > quicker than waiting for someone to fix the headers in question. > > Yes, I could do that - I have done that already for curses.h. But I > still think it sucks badly that there is a variable named 'class', and I > still think it should be changed. A really kludgy workaround would be to make a strictly C module for handling that header, then link your C++ to it. I do agree that it sucks though. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message