Hi,
Javier Martín <[EMAIL PROTECTED]> writes:
>> Anyway, since "they" are more likely to maintain the code in
>> the long run than you, in general, the question is whether
>> the code is more likely to become buggy by their hacking on
>> it, if it follows project coding style or someone else's
>> (your) "safer" coding style. Likely it's safer if using a
>> consistent programming style. Although I personally don't
>> see that it's very helpful to have a style that makes things
>> down to the order of "==" arguments be consistent within the
>> project; haphazard only slows reading the tiniest bit, and I
>> don't think it makes a different what order the arguments are...
>
> Hmm... I was partially expecting a flamefest to start. Pity ^^
> Well, let's spill a little napalm: the GNU style bracing is extremely
> silly!! Why the hell are the "if" and "else" blocks indented differently
> in this example?
> if (condition)
> return 0;
> else
> {
> return -1;
> }
> Nah, I'm not really bringing that issue, I was just joking, and in fact
> I'm reconsidering my objections to the operator== arguments order rule,
> even though I still consider my style safer and more sensible. If
> someone else wants to express their opinion on that issue, do it fast
> before I completely submit to Master Marco's will :D
Please don't be sarcastic, start flame wars or call names. It will not
help anyone.
--
Marco
_______________________________________________
Grub-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/grub-devel
