From: "Chris Friesen" <cfriesen@nortel.com>
To: ptb@inv.it.uc3m.es
Cc: Andreas Schwab <schwab@suse.de>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: time_is_after_jiffies misnomer
Date: Tue, 16 Dec 2008 13:29:55 -0600 [thread overview]
Message-ID: <494801B3.9060203@nortel.com> (raw)
In-Reply-To: <200812161632.mBGGWh213629@inv.it.uc3m.es>
Peter T. Breuer wrote:
> Forgive me, but you don't seem to really be taking it on board here
> either ... what it SAYS to an english reader is the opposite of what
> you intend it to MEAN, unfortunately :(.
time_is_after_jiffies(foo) means: time "foo" is after the current value
of the variable "jiffies" (which is used throughout the kernel as the
current time).
You are interpreting it as: the current time is after time "foo" (which
is in jiffies).
The reason why your interpretation is incorrect is that "jiffies" is a
specific variable in and of itself, and not a modifier for "foo".
> So how about keeping the current macro
> names but gradually phasing them out in favour of a parallel set of
> alternatives, which could be
>
> current_time_is_before_jiffies(foo)
>
> ?? That reads fine in english and this time it means what it says!
You're using "jiffies" as a modifier for "foo", when it is actually a
separate variable. This makes your version just as ambiguous.
If you really want to change it, removing "jiffies" from the name (and
thus removing any ambiguity) may make more sense. Something like:
time_is_after(foo)
which would mean that the current value of "jiffies" is after "foo".
Chris
next prev parent reply other threads:[~2008-12-16 19:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 11:31 time_is_after_jiffies misnomer Peter T. Breuer
2008-12-16 14:46 ` Johannes Weiner
2008-12-16 15:17 ` Peter T. Breuer
2008-12-16 16:18 ` Andreas Schwab
2008-12-16 16:32 ` Peter T. Breuer
2008-12-16 19:29 ` Chris Friesen [this message]
2008-12-16 20:33 ` Johannes Weiner
2008-12-18 7:38 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2008-12-16 16:04 Peter T. Breuer
2008-12-16 16:13 ` Pekka Enberg
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=494801B3.9060203@nortel.com \
--to=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ptb@inv.it.uc3m.es \
--cc=schwab@suse.de \
/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