Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 93260 invoked by uid 500); 17 Apr 2003 00:55:16 -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 93247 invoked from network); 17 Apr 2003 00:55:16 -0000 Message-ID: <00d601c3047b$efe70890$7500a8c0@goliath> From: "David Reid" To: "APR Dev List" References: <5.2.0.9.2.20030415171425.02099ec8@pop3.rowe-clan.net> <20030415215859.GA2208@manyfish.co.uk> <5.2.0.9.2.20030415171425.02099ec8@pop3.rowe-clan.net> <5.2.0.9.2.20030415212716.01229bf8@pop3.rowe-clan.net> <20030416191151.GB30157@manyfish.co.uk> Subject: Re: HEAD and releases Date: Thu, 17 Apr 2003 01:54:44 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > I tried to fix apr_generate_random_bytes() to use size_t already. I'd > also like to reorder struct apr_sockaddr_t to make it binary compatible > across !APR_HAVE_IPV6 and APR_HAVE_IPV6, which requires breaking binary > compatibility with 0.9.2. Presumably this also means a more consistent api, so +1 for the socket change. 0.9.x does not mean we're backward compatible :( 1.0 on the other hand... david