From owner-freebsd-current Fri Apr 14 16:02:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA11822 for current-outgoing; Fri, 14 Apr 1995 16:02:25 -0700 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA11816 for ; Fri, 14 Apr 1995 16:02:17 -0700 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id AAA19029; Sat, 15 Apr 1995 00:01:29 +0100 From: Paul Richards Message-Id: <199504142301.AAA19029@isl.cf.ac.uk> Subject: Re: deamon To: bde@zeta.org.au (Bruce Evans) Date: Sat, 15 Apr 1995 00:01:28 +0100 (BST) Cc: FreeBSD-current@FreeBSD.org In-Reply-To: <199504142243.IAA24634@godzilla.zeta.org.au> from "Bruce Evans" at Apr 15, 95 08:43:50 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 806 Sender: current-owner@FreeBSD.org Precedence: bulk In reply to Bruce Evans who said > > >There's a daemon() defined in stdlib.h that's new with 4.4BSD and it > >clashes with a char array defined in procmail. Anyone know anything > >about this? Should it really be declared in stdlib.h? > > No. It isn't standard. This example shows the type of thing that goes > wrong when standard headers are polluted. So we need to sanitise stdlib.h, how do we best deal with this then. The hash code is in the stdlib area of libc but has it's own specific header. Can we do the same for other non-standard parts of libc. -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff.