From owner-freebsd-arch Wed Jul 25 9:24: 7 2001 Delivered-To: freebsd-arch@freebsd.org Received: from assaris.sics.se (h122n4fls32o892.telia.com [213.64.47.122]) by hub.freebsd.org (Postfix) with ESMTP id 767E037B41D for ; Wed, 25 Jul 2001 09:23:58 -0700 (PDT) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id SAA29184; Wed, 25 Jul 2001 18:23:37 +0200 (CEST) (envelope-from assar) To: Mike Heffner Cc: Warner Losh , arch@FreeBSD.ORG Subject: Re: Making glob(3) portable (was Re: Importing lukemftpd) References: From: Assar Westerlund Date: 25 Jul 2001 18:23:35 +0200 In-Reply-To: Mike Heffner's message of "Tue, 24 Jul 2001 23:41:00 -0400 (EDT)" Message-ID: <5ly9pduge0.fsf@assaris.sics.se> Lines: 15 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Heffner writes: > In what way is it not as bad? I agree that we don't have all the error values > that NetBSD and OpenBSD have, but using a different one for this scenario than > what the other *BSDs use is not very portable either. The state where the FreeBSD error code had the same name as the Net/OpenBSD option was bad, because then code using GLOB_LIMIT would just build and fail badly at run-time. > IMO, removing GLOB_LIMITHIT, or whatever, and just using GLOB_NOSPACE with > errno=0 would be the first step in the direction of portability. Sure, we can do that. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message