Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 69919 invoked by uid 500); 6 Mar 2000 23:13:16 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 69900 invoked from network); 6 Mar 2000 23:13:16 -0000 Message-ID: <011b01bf87c1$53ec3490$0a1aa8c0@jetnet.co.uk> From: "David Reid" To: References: Subject: Re: returning statuses in apr Date: Mon, 6 Mar 2000 23:11:38 -0000 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.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N To be honest it makes sense to me as well. However, we also need to include the proviso that if so much as a single supported platform implements the function in such a way that calling it may return an error code then it should be returning an ap_status_t on all platforms. d. ----- Original Message ----- From: "Greg Stein" To: Sent: Monday, March 06, 2000 11:11 PM Subject: Re: returning statuses in apr > Let's modify the Design Statement to be: > > "An APR function may return ap_status_t or void. Nothing else. Return > values should be handled through [out] parameters." > > > Cheers, > -g > > On Sun, 5 Mar 2000 rbb@apache.org wrote: > > > > Every discussion we had about status codes said EVERY function returns a > > status code. We could remove this requirement, but I would rather not. > > It makes it very easy for people using APR functions to ALWAYS know the > > basic setup for an apr function. > > > > Ryan > > > > On Sun, 5 Mar 2000, Life is hard, and then you die. wrote: > > > > > > > > Looking at lib/apr/lib/apr_md5.c I have a question: > > > > > > Why are the functions returning ap_status_t when nothing can go > > > wrong? (i.e. all they ever return is APR_SUCCESS). Any reason > > > not to revert back to returning void? I vaguely remember various > > > discussions around return values, but I don't recall (and couldn't > > > find) anything about having *every* function return a status. > > > > > > The cvs log entry where this happened reads > > > > > > Begin to update apr/lib files to follow the standard APR function format. > > > This is the incredibly low hanging fruit, where all I am doing is > > > standardizing the return codes for functions that already returned int's. > > > > > > but the functions returned void before... (with the exception of > > > ap_validate_password(), but that's not what I'm talking about). > > > > > > > > > Cheers, > > > > > > Ronald > > > > > > > > > > > > Come to the first official Apache Software Foundation > > Conference!!! > > > > ____________________________________________________________________________ ___ > > Ryan Bloom rbb@apache.org > > 406 29th St. > > San Francisco, CA 94131 > > -------------------------------------------------------------------------- ----- > > > > -- > Greg Stein, http://www.lyra.org/ > >