all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
Cc: ams@gnu.org, Ryan Yeske <rcyeske@gmail.com>, emacs-devel@gnu.org
Subject: Re: rcirc bug
Date: Sun, 10 Sep 2006 22:57:26 -0400	[thread overview]
Message-ID: <87irjvxg89.fsf@furball.mit.edu> (raw)
In-Reply-To: <E1GLi1G-0008C9-1d@fencepost.gnu.org> (Richard Stallman's message of "Fri\, 08 Sep 2006 11\:11\:50 -0400")

Richard Stallman <rms@gnu.org> writes:

> I think it would be better to change pushnew to expand
> into code that does not call any cl functions.  Then programs
> that load cl at compile time could use pushnew without problems.

Is there really a problem?  Can someone tell me how to reproduce this
with a simple test case?  I tried made a file with the following
contents:

  (eval-when-compile (require 'cl))
  (defvar foo nil)
  (defun foobar () (interactive) (pushnew 1 foo))
 
Upon byte compiling and loading the byte-compiled file, `M-x foobar'
seemed to work fine.

Didn't the rcirc bug turn out to come from another source (incorrect
use of `case')?

  parent reply	other threads:[~2006-09-11  2:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04 13:51 rcirc bug Alfred M. Szmidt
2006-09-05  9:42 ` Richard Stallman
2006-09-05 21:27 ` Ryan Yeske
2006-09-05 21:37   ` Alfred M. Szmidt
2006-09-05 21:44     ` Ryan Yeske
2006-09-06 19:06     ` Richard Stallman
2006-09-06 19:13       ` Ryan Yeske
2006-09-07 23:19     ` Ryan Yeske
2006-09-08 15:11       ` Richard Stallman
2006-09-08 15:30         ` Drew Adams
2006-09-11  2:57         ` Chong Yidong [this message]
2006-09-11 15:17           ` Stuart D. Herring
2006-09-11 19:57           ` Richard Stallman
2006-09-05 21:44   ` Magnus Henoch
2006-09-07 20:59     ` Chong Yidong
2006-09-07 21:11     ` Stefan Monnier
2006-09-05 21:46   ` Stefan Monnier

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=87irjvxg89.fsf@furball.mit.edu \
    --to=cyd@stupidchicken.com \
    --cc=ams@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rcyeske@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.