Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 91715 invoked by uid 500); 22 Oct 2002 07:00:02 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 91704 invoked from network); 22 Oct 2002 07:00:02 -0000 Date: Tue, 22 Oct 2002 00:00:09 -0700 From: Aaron Bannert To: dev@apr.apache.org Subject: Re: cvs commit: apr/memory/unix apr_pools.c Message-ID: <20021022070008.GW31238@clove.org> Mail-Followup-To: Aaron Bannert , dev@apr.apache.org References: <20021022051748.GT31238@clove.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, Oct 22, 2002 at 01:49:03AM -0400, Ryan Bloom wrote: > Because there is a difference between unset and NULL value. One of them > was specifically set by the program, the other is a programmer trying to > query for a value that was never set. They are two different cases. This > is the time to break the API, before the 1.0 release. This is just a design difference. Most shells don't make a difference between unset and NULL-value. This problem hasn't come up before, and you haven't provided a concrete reason why it is broken now. -aaron