From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/sparc] Add handling of stack-check probes
Date: Thu, 29 Mar 2007 04:21:00 -0000 [thread overview]
Message-ID: <umz1w8ytx.fsf@gnu.org> (raw)
In-Reply-To: <20070328225013.GN3866@adacore.com> (message from Joel Brobecker on Wed, 28 Mar 2007 15:50:13 -0700)
> Date: Wed, 28 Mar 2007 15:50:13 -0700
> From: Joel Brobecker <brobecker@adacore.com>
>
> PS: Do other people think that it is simpler for the human brain to understand
> if (pc >= current_pc)
> than
> if (current_pc <= pc)
>
> In other words, the boundary value is put on the rhs of the condition,
> and the variable value is put on the lhs... It's just an aesthetic
> consideration, but I can change it if others agree.
I prefer the variable to be on the left and the boundary on the right.
The only case where it is justified to reverse the order is when you
use ==, to avoid the frequent typo that uses only one `='.
next prev parent reply other threads:[~2007-03-29 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 22:49 Joel Brobecker
2007-03-29 4:21 ` Eli Zaretskii [this message]
2007-04-10 15:34 ` Daniel Jacobowitz
2007-04-11 7:11 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=umz1w8ytx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox