On Thu, Mar 27, 2025 at 11:29:16AM +0100, Johannes Schindelin wrote:
> Hi Taylor,
>
> On Wed, 26 Mar 2025, Taylor Blau wrote:
>
> > On Tue, Mar 25, 2025 at 11:32:12PM +0000, Johannes Schindelin via GitGitGadget wrote:
> > > diff --git a/compat/regex/regex_internal.c b/compat/regex/regex_internal.c
> > > index ec5cc5d2dd1..7672583bf7e 100644
> > > --- a/compat/regex/regex_internal.c
> > > +++ b/compat/regex/regex_internal.c
> > > @@ -1231,9 +1231,10 @@ re_node_set_merge (re_node_set *dest, const re_node_set *src)
> > > for (sbase = dest->nelem + 2 * src->nelem,
> > > is = src->nelem - 1, id = dest->nelem - 1; is >= 0 && id >= 0; )
> > > {
> > > - if (dest->elems[id] == src->elems[is])
> > > - is--, id--;
> > > - else if (dest->elems[id] < src->elems[is])
> > > + if (dest->elems[id] == src->elems[is]) {
> > > + is--;
> > > + id--;
> > > + } else if (dest->elems[id] < src->elems[is])
> >
> > Should the other arms of this conditional have matching curly-braces?
>
> No. Have a look around in that file, that's not the coding convention.
I was just about to respond that even though it breaks the convention,
that we should encourage good hygeine by ensuring new code follows the
CodingGuidelines, even if it looks wonky in the context of the rest of
the file.
But this is compat/regex code, which clearly does not need to follow the
convention. Sorry about that!
Thanks,
Taylor
