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

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

> sigurd@12move.de (Karl Pflästerer) writes:

>> 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

> I think the variables I listed are safe to delete.  But in general I
> don't think there's any way to determine it automatically.

ACK.  Because of that I posted them here instead of a big patch :-)

Maybe we could try it in small steps; always delete 5 wait some days and
remove the next 5.

> For example the function `mm-file-name-collapse-whitespace' isn't used
> anywhere -- but its purpose is that you can add it to the hook
> `mm-file-name-rewrite-functions', so it clearly shouldn't be removed.

Yes with functions it gets even harder to decide which one aren't used
anymore.


   KP

-- 
 `Beware the Jabberwock, my son!
     The jaws that bite, the claws that catch!
  Beware the Jubjub bird, and shun
    The frumious Bandersnatch!'   "Lewis Carroll" "Jabberwocky"



  reply	other threads:[~2004-02-13 23:11 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
2004-02-13 22:16         ` Jesper Harder
2004-02-13 23:11           ` Karl Pflästerer [this message]
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=m3oes2tw65.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).