Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of bojan@rexursive.com
 designates 150.101.121.179 as permitted sender)
Subject: Re: dbd p[v]b functions problem
From: Bojan Smojver <bojan@rexursive.com>
To: Bob Rossi <bob@brasko.net>
Cc: dev@apr.apache.org
In-Reply-To: <20100204231429.GC20966@brasko.net>
References: <20100204224416.GA20966@brasko.net>
	 <1265323919.1858.3.camel@shrek.rexursive.com>
	 <20100204230608.GB20966@brasko.net>
	 <1265324987.1858.5.camel@shrek.rexursive.com>
	 <20100204231429.GC20966@brasko.net>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 05 Feb 2010 10:23:33 +1100
Message-ID: <1265325813.1858.14.camel@shrek.rexursive.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Thu, 2010-02-04 at 18:14 -0500, Bob Rossi wrote:
> OK, do you like what I'm suggesting? An interface that takes a
> va_list, that behaves just like printf...
> 
> If you like it, what would you like the name of the function to be
> called? Any pointers?

No opinion, to be honest, because I rarely use the whole thing these
days. The best thing to do is:

1. Open a bug report and put you patch in it (so it doesn't slip through
the cracks on the list).

2. Let the list know (attach the patch) that you are proposing a change
or addition in API for 2.0, explain why, how etc. and you'll get
feedback from folks on the list.

Once that's all discussed and decided, someone will then commit the
patch for you.

PS. Although our rules allow all API to be broken on a major release, if
something worked in a previous major release and API can be added
instead of replaced, this (IMHO) is a better way of going about things.

-- 
Bojan