GNU bug report logs - #6663
#if 0 blocks in source code

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Christoph <cschol2112 <at> googlemail.com>
Subject: bug#6663: closed (Re: bug#6663: #if 0 blocks in source code)
Date: Wed, 06 Feb 2013 19:15:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#6663: #if 0 blocks in source code

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 6663 <at> debbugs.gnu.org.

-- 
6663: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6663
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Glenn Morris <rgm <at> gnu.org>
To: 6663-done <at> debbugs.gnu.org
Subject: Re: bug#6663: #if 0 blocks in source code
Date: Wed, 06 Feb 2013 14:13:00 -0500

Sorry, I see no value in keeping this report open.
The #if 0s will either decay with time or they wont. Having a bug report
about it won't change anything.
Closing as wontfix.

[Message part 3 (message/rfc822, inline)]

From: Christoph <cschol2112 <at> googlemail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: #if 0 blocks in source code
Date: Sat, 17 Jul 2010 16:10:42 -0600

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?

Christoph

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.