"Keller, Jacob E" <jacob.e.kel...@intel.com> writes:
> On Fri, 2014-07-11 at 08:04 -0700, Junio C Hamano wrote:
>> > +static int tag_sort = 0;
>> Please do not initialize variables in bss segment to 0 by hand.
>> If this variable is meant to take one of these *CMP_SORT values
>> defined as macro later in this file, it is better to define this
>> variable somewhere after and close to the definitions of the macros.
>> Perhaps immediately after the "struct tag_filter" is declared?
> I put it just above the struct tag_filter now, as this puts it right
> below the #defines regarding it's value.
Either would be fine, but just to clarify.
Because these macro definitions are for the .sort field of that
structure, and the new tag_sort variable is the second user of that
macro, my suggestion to put it _after_ was to be in line with "add
new things at the end, when there is no compelling reason not to"
>> When there is no reason to have things in a particular order, it is
>> customary to add new things at the end, not in the front, unless the
>> new thing is so much more important than everything else---but then
>> we are no longer talking about the case where there is no reason to
>> have things in a particular order ;-).
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html