Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <41AB7545.6040106@stason.org>
Date: Mon, 29 Nov 2004 14:15:17 -0500
From: Stas Bekman <stas@stason.org>
Organization: Hope, Humanized
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913
MIME-Version: 1.0
To: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
Cc: dev@apr.apache.org
Subject: Re: svn commit: r106663 - /apr/apr/trunk/CHANGES
    /apr/apr/trunk/include/apr_file_io.h
References: <20041126212638.63419.qmail@minotaur.apache.org>
 <6.2.0.14.2.20041128231151.05686b28@pop3.rowe-clan.net>
 <41AB5346.7090202@stason.org>
 <6.2.0.14.2.20041129111159.04a63988@pop3.rowe-clan.net>
 <41AB6032.2030900@stason.org>
 <6.2.0.14.2.20041129122533.03f40150@pop3.rowe-clan.net>
In-Reply-To: <6.2.0.14.2.20041129122533.03f40150@pop3.rowe-clan.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

William A. Rowe, Jr. wrote:
> At 11:45 AM 11/29/2004, Stas Bekman wrote:
> 
>>William A. Rowe, Jr. wrote:
>>
>>>At 10:50 AM 11/29/2004, Stas Bekman wrote:
>>>
>>>
>>>>Also should the deprecated macros stay in this file or can those be moved to some dedicated file to reduce the noise?
>>>
>>>They stay in place.  During the next major+1 bump, the RM
>>>trawls through the files looking for @deprecated, and simply
>>>strips them out.  
>>
>>That's not possible with this particular change, since everything (APR/httpd) still uses the old macros.
> 
> 
> No, it's a requirement when we push major+1.  Then again,
> httpd may stay with 1.x, or may have a prerequisite 1.1
> (meaning we assume your change is there) or it may even

So when will it be possible to know whether it'll be in or not? If someone 
decides to remove those later, why do I waste my time?

> move to 2.x - in which case we -must- update all occurrences 
> within httpd.

Understood.

> There is no reason to keep using the old symbols in apr[-util/-iconv]
> so feel free to start migrating those.

I'll be working on symbols that I touch, at the moment I don't have to 
time to work on other things. Once mod_perl 2.0 is out I may be able to 
spend more time on other things.

>>>The way doxygen works, you would not want
>>>these moving out of scope to another file.
>>
>>Is there a way to put them in a different file and tell doxygen that the following entries really belong to a different file?
> 
> 
> 1. it isn't pretty and
> 
> 2. you can't force a user to include another file from minor
>    to minor bump.  Their code should keep compiling w/o changes.
> 
> Please don't worry that this seems 'polluted' - the next major
> bump cleans this all out.  In the meantime, if they look for
> these symbols grep APR_FOO include/* they should find the old
> and new flavors in the same file, helping them with their own
> migration tasks.

Good point.


-- 
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com