From: Francis Litterio <franl@world.std.com>
Subject: Re: push and pop
Date: Sun, 09 Jan 2005 14:04:51 -0500 [thread overview]
Message-ID: <ud5weju6o.fsf@world.std.com> (raw)
In-Reply-To: 1105293235.16765.10.camel@slider
JD Smith wrote:
> Is there a technical reason the subr push and pop can't behave
> like the cl versions?
The biggest reason is that it would violate an interface contract. You
aren't seriously proposing changing the semantics of the push and pop
subrs?
--
Francis Litterio
franl <at> world . std . com
next prev parent reply other threads:[~2005-01-09 19:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 18:21 push and pop JD Smith
2005-01-07 19:39 ` David Kastrup
2005-01-07 20:23 ` Stefan Monnier
2005-01-07 21:15 ` JD Smith
2005-01-08 2:19 ` Miles Bader
2005-01-08 15:34 ` Richard Stallman
2005-01-09 17:53 ` JD Smith
2005-01-09 19:04 ` Francis Litterio [this message]
2005-01-09 19:42 ` Luc Teirlinck
2005-01-09 19:56 ` David Kastrup
2005-01-10 20:27 ` Richard Stallman
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=ud5weju6o.fsf@world.std.com \
--to=franl@world.std.com \
/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).