Gnus development mailing list
 help / color / mirror / Atom feed
From: sigurd@12move.de (Karl Pflästerer)
Subject: Re: Orphaned symbols?
Date: Fri, 13 Feb 2004 22:25:13 +0100	[thread overview]
Message-ID: <m365eavfpl.fsf@hamster.pflaesterer.de> (raw)
In-Reply-To: <m3u11viruj.fsf@defun.localdomain>

On 13 Feb 2004, Jesper Harder <- harder@ifa.au.dk wrote:

> I don't think these are used:

[Variables]

> But it's not necessarily trivial to tell, because you can reference a
> variable by constructing the name dynamically -- that's the case for
> some of the ones you listed.

Yes; especially in gnus-article that's used heavily (the functions are
defined with out gnus- prefix and it's added somewhere); not very nice.

> These aren't actually used:

> | ietf-drums-dot-atext-token -> ietf-drums.el
> | ietf-drums-qtext-token -> ietf-drums.el
> | ietf-drums-quote-token -> ietf-drums.el
> | ietf-drums-specials-token -> ietf-drums.el

> but it makes sense to keep them.  They were probably included to
> define all the BNF tokens in the RFC.

Is there no possibility to decide which variables could safely be
deleted?  Some of the vars I found aren't used anywhere; they make it
only harder to understand the code.  I also find a bunch of functions
which are only defined but never used (for them it's even harder to
decide if they don't get somewhere defined dynamically).  If we never
try to find them we will have garbage in the code.


   KP

-- 
If you have nothing to say on a subject, replying with a line such as,
"I agree with this." puts you in the TO:'s for all future messages, and
establishes you as "one who really cares", if not an actual expert, on
the topic at hand.         -- from the Symbolics Guidelines for Sending Mail



  reply	other threads:[~2004-02-13 21:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-10 20:28 Karl Pflästerer
2004-02-12 14:03 ` Reiner Steib
2004-02-12 21:03   ` Karl Pflästerer
2004-02-12 22:02     ` Reiner Steib
2004-02-13  3:24     ` Jesper Harder
2004-02-13 21:25       ` Karl Pflästerer [this message]
2004-02-13 22:16         ` Jesper Harder
2004-02-13 23:11           ` Karl Pflästerer
2004-02-14 18:23       ` Kai Grossjohann

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=m365eavfpl.fsf@hamster.pflaesterer.de \
    --to=sigurd@12move.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;
as well as URLs for NNTP newsgroup(s).