Re: [PATCH]: notification progress improvement/fixes (issue #901)
From: David Anderson <david.anderson_at_calixo.net>
Date: 2005-08-31 03:00:32 CEST
Stefan Küng wrote:
As I accidentally rediscovered part of the bug you're fixing here and
Other commiters: meta-reviews most welcome, I'm new to this.
> Fix stack bug, improve the progress notification callback feature.
This patch should be just a fixing patch. Thus, this is no real
> + apr_pool_t *pool,
Pools are usually the last parameter of functions and callbacks. Any
> + * In order to avoid backward compatibility problems, clients should use
Don't give a choice: "In order to ease future compatibility, clients
> @@ -439,6 +417,23 @@
allocate, then initialize ;-).
> +* The current implementation never returns error, but callers should
No need to speak of implementation in public API documentation. The
> + neonprogress_baton_t * neonprogress_baton = (neonprogress_baton_t *)baton;
You can make this pointer const, to be nicely strict. Also, no space
> @@ -593,6 +601,8 @@
Same comment about the extra space.
I've commited your fix, modulo these changes, as r16010, with a followup
While I'm at it, I'll review your feature patch (hopefully with a little
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.