From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Orphaned symbols?
Date: Thu, 12 Feb 2004 15:03:58 +0100 [thread overview]
Message-ID: <v9r7x0fl81.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3ptcmitex.fsf@hamster.pflaesterer.de>
On Tue, Feb 10 2004, Karl Pflästerer wrote:
> I got nosy and searched for variable names which were not used anywhere
> in the code. I found 93 names (and some more functions).
Huh, this number seems quite high.
> Before I post all these names in which libraries do I also have to
> look for usage of variables?
I'd suggest to post the list, maybe someone has a glue about their
potential usage in other packages.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-02-12 14:03 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 [this message]
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
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=v9r7x0fl81.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.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).