From owner-cvs-all  Fri Dec 18 07:44:59 1998
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA21831
          for cvs-all-outgoing; Fri, 18 Dec 1998 07:44:59 -0800 (PST)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21814;
          Fri, 18 Dec 1998 07:44:49 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA29685;
	Sat, 19 Dec 1998 02:44:36 +1100
Date: Sat, 19 Dec 1998 02:44:36 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199812181544.CAA29685@godzilla.zeta.org.au>
To: des@flood.ping.uio.no, des@FreeBSD.ORG
Subject: Re: cvs commit: src/lib/libfetch Makefile common.c common.h ftp.c          http.c
Cc: cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

>>   Rename fetchConnect to _fetch_connect since it's internal.
>
>though if I understand the standard correctly, all the _fetch_xxx
>should be renamed to either __fetch_xxx or _Fetch_xxx since their
>scope is wider than file scope. Any language lawyers care to comment?

The "should" clause doesn't follow from the "since" clause.
All identifiers that begin with an underscore are reserved for use
as identifiers with file scope.  Therefore, the implementation can
use such identifiers at file scope without restriction.  OTOH, the
implementation can't use such identifiers at non-file scope if such
use could conflict with an application identifier.  This is the only
restriction, and it only prevents use of identifiers starting with
"_[a-z0-9]" in macros that may be used by applications.

Bruce

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