Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 60859 invoked from network); 8 Jul 2008 21:29:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Jul 2008 21:29:02 -0000 Received: (qmail 89603 invoked by uid 500); 8 Jul 2008 21:29:01 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 89563 invoked by uid 500); 8 Jul 2008 21:29:01 -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 89547 invoked by uid 99); 8 Jul 2008 21:29:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jul 2008 14:29:01 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.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; Tue, 08 Jul 2008 21:28:09 +0000 Received: (qmail 22949 invoked from network); 8 Jul 2008 21:26:36 -0000 Received: from unknown (166.128.186.100) by smtpauth17.prod.mesa1.secureserver.net (64.202.165.29) with ESMTP; 08 Jul 2008 21:26:35 -0000 Message-ID: <4873DBF0.7080206@rowe-clan.net> Date: Tue, 08 Jul 2008 16:28:16 -0500 From: "William A. Rowe, Jr." User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Mladen Turk CC: Sander Striker , dev@apr.apache.org Subject: Re: apr_pool_create_core_ex, WAS: Re: svn commit: r647384 - in /apr/apr/trunk: CHANGES include/apr_pools.h memory/unix/apr_pools.c References: <487374B4.2030504@rowe-clan.net> <48737F6C.70903@apache.org> <4873836C.909@rowe-clan.net> <48738698.5030602@apache.org> In-Reply-To: <48738698.5030602@apache.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Mladen Turk wrote: > William A. Rowe, Jr. wrote: >> Mladen Turk wrote: >>> >>> Any problems renaming the API in 1.3.x as well? >> >> Yup, it shipped. So we can @deprecate your original choice of name >> and add any new name that's appropriate. >> > > Does depreciation means the function must be implemented? > I suppose it should, so it'll simply call the renamed one. Call the well-named function from the deprecated one, yes. It's the pattern that is repeated throughout the API. When the deprecated fn disappears in 2.0, it has no impact on the legitimate one. > What a mess ?!# :( That's called strict versioning, and that's why I *begged* for careful review before 1.3.0 was released.