Date: Sun, 3 Jun 2001 22:18:18 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: Mike Barcroft <mike@q9media.com>, Bruce Evans <bde@zeta.org.au> Cc: <freebsd-arch@FreeBSD.ORG> Subject: Re: Removing __P() (was Re: whois(1) patch) Message-ID: <p05100e03b7409e2eb13d@[128.113.24.47]> In-Reply-To: <B7405488.C0D%mike@q9media.com> References: <B7405488.C0D%mike@q9media.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 8:54 PM -0400 6/3/01, Mike Barcroft wrote: >Sorry, I didn't state that question very clearly. I want >to silence warnings with WARNS=2 enabled by converting >some variables to const char *. Since I'm converting >variables to ANSI C types, it makes no sense to carry along >the __P() support shims because it won't compile on K&R anyway. >Am I correct in my assertion? This topic has come up before on the developers list, and the consensus has been that it's alright to do ANSI-fication at a individual program level, as long as you have some other reason to be making "declaration changes" in that same program. That consensus has not been unanimous, but it has been the consensus whenever I've seen it discussed. ANSI-fication of any system include libraries (anything in /usr/include) is pretty much universally discouraged, and might possibly result in some hostility... -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05100e03b7409e2eb13d>