From: Dave Love <d.love@dl.ac.uk>
Subject: inconsistent alloca and getopt files
Date: 24 Nov 2002 19:43:55 +0000 [thread overview]
Message-ID: <rzqisymda83.fsf@albion.dl.ac.uk> (raw)
alloca.c and getopt.c in Emacs are different from the ones in GNU
hello, for instance. I don't know where the canonical sources are
supposed to be now, and it's not clear to me where in the GNU
distribution one should look for copies of these and similar files to
include in other programs, but I think things should be made
consistent.
I think it would be useful to have a distribution of routines you'd
typically want to provide for when the target doesn't have (correct)
implementations, perhaps a canonical libiberty. The Automake
distribution be a good place to have them, but I assume there's a good
reason that's not done now.
reply other threads:[~2002-11-24 19:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rzqisymda83.fsf@albion.dl.ac.uk \
--to=d.love@dl.ac.uk \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).