all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Christoph <cschol2112@googlemail.com>
Cc: 6663@debbugs.gnu.org
Subject: bug#6663: #if 0 blocks in source code
Date: Thu, 22 Jul 2010 14:31:34 +0200	[thread overview]
Message-ID: <AANLkTilvSYqi9AgqQiGINJDGxHJM6uGf3VMysQG5vkh_@mail.gmail.com> (raw)
In-Reply-To: <864ofxiwt9.fsf@gmail.com>

On Sun, Jul 18, 2010 at 00:10, Christoph <cschol2112@googlemail.com> wrote:

> I noticed a couple of #if 0 blocks in keyboard.c, which have explicit comments
> that the code within the block is obsolete. A quick grep "#if 0" showed
> about 200 instances of disabled or obsolete code in files in the src directory.
>
> Should these instances be cleaned up?

Not blindly, no.

Some of these code is not obsolete, it's just that it has not been
made to work yet (ISTR there's such code in parts of the w32 image
support, for example, but I could be wrong).

Some of it is indeed obsolete, but (I think) it was felt that having
it around to see would preclude people reinventing tried-and-discarded
ways. That was perhaps more relevant with CVS than Bazaar (or not,
because we still don't have a web interface to easily see past
versions, and relying on bzr blame is clumsy).

In other words, IMHO the answer is that some of these #if 0 blocks
could and should be removed, but you'll have to look at them, exercise
good sense and perhaps ask. Which is why most of them has never been
removed, I suppose :-)  Though lately, Dan and Glenn have spearheaded
a big cleanup, so times, they are a-changing.

    Juanma





  reply	other threads:[~2010-07-22 12:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-17 22:10 bug#6663: #if 0 blocks in source code Christoph
2010-07-22 12:31 ` Juanma Barranquero [this message]
2013-02-06 19:13   ` Glenn Morris

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=AANLkTilvSYqi9AgqQiGINJDGxHJM6uGf3VMysQG5vkh_@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=6663@debbugs.gnu.org \
    --cc=cschol2112@googlemail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.