Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Simple lisp question
Date: Mon, 20 Dec 2010 18:04:19 +0100	[thread overview]
Message-ID: <m3pqswe5po.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m2aak0z8rw.fsf@verilab.com>

Tommy Kelly <tommy.kelly@verilab.com> writes:

> In other words, why is the setting to nil of nimap-incoming-split-list
> and news-articles done differently? Just a coding quirk, or a deep and
> mysterious reason?

To the compiler, it's the same, but some people prefer to bind stuff
explicitly to nil, if nil is what the variable is supposed to be, as
opposed to implicitly binding it to nil to signal that it's going to get
its real value further ahead.

So it's a style issue.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




      reply	other threads:[~2010-12-20 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 16:52 Tommy Kelly
2010-12-20 17:04 ` Lars Magne Ingebrigtsen [this message]

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=m3pqswe5po.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).