Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 71552 invoked by uid 500); 4 May 2001 12:54:58 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 71336 invoked from network); 4 May 2001 12:54:48 -0000 From: Jim Jagielski Message-Id: <200105041254.IAA22178@devsys.jaguNET.com> Subject: Re: cvs commit: httpd-2.0/server/mpm/threaded threaded.c To: new-httpd@apache.org Date: Fri, 4 May 2001 08:54:45 -0400 (EDT) Reply-To: jim@jaguNET.com In-Reply-To: from "Jeff Trawick" at May 04, 2001 07:53:48 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Jeff Trawick wrote: > > Maybe my point wasn't taken. Rephrased more simply. > > INT_MAX still has to be the largest value that can be stored in a > signed int, so > > on a 16-bit machine, INT_MAX will be 32767 > on a 32-bit machine, INT_MAX will be 2billion or so > > Therefore, bringing "32767" into the discussion means bringing > Apache-on-16-bit into the discussion. > > I seriously doubt we would want to hack up Apache *and* APR *and* > expat *and* PCRE *and* whatever else to work on a 16-bit machine. I > seriously doubt that any publically released version of Apache has > ever worked on a 16-bit machine. > > So let's put the "32767" part of the discussion to rest. > A machine can be ANSI compliant and have INT_MAX == 32767 and have as many bits as it wants. All ANSI does is set a lower limit to INT_MAX. ANSI doesn't define the number of bits per any type, except setting that char must be at least 8 bits. At that point, ANSI does not bring "number of bits" into any discussions at all (IIRC). ANSI only guarantees that signed ints will go up to 32767. If you need them to be higher, then ANSI doesn't do that for you, and we need to make sure that we have a large enough range. It ain't bits at all, but scale. Of course, in the real world, INT_MAX of 32767 implies 16bit, but it's just these kinds of assumptions that create problems in the 64bit world. -- =========================================================================== Jim Jagielski [|] jim@jaguNET.com [|] http://www.jaguNET.com/ "Hell is hot, that's never been disputed by anybody."