Philip Martin wrote:
> Greg Stein <gst...@gmail.com> writes:
>
> > On Wed, May 5, 2010 at 10:27, <phi...@apache.org> wrote:
> >>...
> >> +++ subversion/trunk/subversion/libsvn_client/commit_util.c Wed May 5
> >> 14:27:45 2010
> >> @@ -1036,7 +1036,7 @@ svn_client__harvest_committables(apr_has
> >> for (i = 0; i < targets->nelts; ++i)
> >> {
> >> const svn_wc_entry_t *entry;
> >> - const char *target_abspath;
> >> + const char *url, *target_abspath;
> >> svn_boolean_t is_added;
> >> svn_error_t *err;
> >
> > Please use one line per variable declaration. Most code follows this
> > pattern, as it is easier to read (especially when initializers are
> > present).
> >
> > (and yes, we don't have a *rule* about this; I'm simply making a request)
>
> I don't see it as an improvement. Is there a consensus that one
> declaration per line is better?
I don't feel we should avoid it particularly. Just have an eye for
what's reasonable in the context.
Quick stats from "grep": We have nearly 900 lines of multiple
uninitialized declarations like this, out of nearly 17000 lines of
simple uninitialized declarations in total. Half our C source files use
this style at least once, the other half don't use it.
- Julian
