From owner-freebsd-arch  Wed Feb 21  5:25: 8 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from assaris.sics.se (assaris.sics.se [193.10.66.234])
	by hub.freebsd.org (Postfix) with ESMTP id 6CAF437B699
	for <arch@FreeBSD.ORG>; Wed, 21 Feb 2001 05:25:04 -0800 (PST)
	(envelope-from assar@assaris.sics.se)
Received: (from assar@localhost)
	by assaris.sics.se (8.9.3/8.9.3) id OAA38202;
	Wed, 21 Feb 2001 14:24:57 +0100 (CET)
	(envelope-from assar)
To: Bruce Evans <bde@zeta.org.au>
Cc: Kris Kennaway <kris@obsecurity.org>, arch@FreeBSD.ORG
Subject: Re: [cgd@netbsd.org: CVS commit: basesrc]
References: <Pine.BSF.4.21.0102211600070.25199-100000@besplex.bde.org>
From: Assar Westerlund <assar@FreeBSD.ORG>
Date: 21 Feb 2001 14:24:57 +0100
In-Reply-To: Bruce Evans's message of "Wed, 21 Feb 2001 16:03:42 +1100 (EST)"
Message-ID: <5l1yssrwwm.fsf@assaris.sics.se>
Lines: 13
User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bruce Evans <bde@zeta.org.au> writes:
> It won't help much with portability.  getprogname() and setprogname()
> are currently even more unportable than __progname, and their names
> don't indicated that they should not be used in applications.

But they're supposed to be used in applications.  They are helpful
when porting BSD programs that use {err,warn}{,x} (thus relying on the
presence of a __progname).  When porting these to non-BSD systems, you
only need to add the trivial implementation of {s,g}etprogname.
Which, I would like to add, was the original rationale for having
these functions.

/assar

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message