Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 6093 invoked from network); 23 Mar 2009 13:16:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Mar 2009 13:16:29 -0000 Received: (qmail 3700 invoked by uid 500); 23 Mar 2009 13:16:28 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 3636 invoked by uid 500); 23 Mar 2009 13:16:28 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 3628 invoked by uid 99); 23 Mar 2009 13:16:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Mar 2009 13:16:28 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [64.202.165.29] (HELO smtpauth17.prod.mesa1.secureserver.net) (64.202.165.29) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 23 Mar 2009 13:16:19 +0000 Received: (qmail 8074 invoked from network); 23 Mar 2009 13:15:57 -0000 Received: from unknown (62.12.12.10) by smtpauth17.prod.mesa1.secureserver.net (64.202.165.29) with ESMTP; 23 Mar 2009 13:15:56 -0000 Message-ID: <49C78B87.3010003@rowe-clan.net> Date: Mon, 23 Mar 2009 14:15:51 +0100 From: "William A. Rowe, Jr." User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Kevac Marko , APR Developer List Subject: Re: apr_memcache flags parameter should be apr_uint32_t, not apr_uint16_t References: <49C6E348.5000800@rowe-clan.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Kevac Marko wrote: > On Mon, Mar 23, 2009 at 4:18 AM, William A. Rowe, Jr. > wrote: >> yes, on all architectures to speak of, 8 or 16 are promoted to 32 bits >> anyways, so anything less than a 32 bit flag arg is absurd. >> >> But we won't/can't address the problem until APR 2.0. > > Why not? It is clearly bug, not just some API change. Memcached flag IS 32 bit. Because you can't change the binary API, we have to stomach our mistakes until the next rev... http://apr.apache.org/versioning.html