Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@myrealbox.com>
Subject: Re: Oort Gnus v0.19 is released
Date: Tue, 29 Apr 2003 00:30:51 +0200	[thread overview]
Message-ID: <m3he8ib6g4.fsf@defun.localdomain> (raw)
In-Reply-To: <iluissycuaw.fsf@latte.josefsson.org> (Simon Josefsson's message of "Mon, 28 Apr 2003 21:10:15 +0200")

Simon Josefsson <jas@extundo.com> writes:

> Jesper Harder <harder@myrealbox.com> writes:
>
>> There is a grain of truth in the warnings, i.e. that pop is a tiny bit
>> less efficient when we don't use the return value -- not that I think
>> anyone would notice the difference.
>
> The warning has been removed, but I'm not sure I agree it had even a
> tiny grain of truth in it -- the docstring for `pop' says "Remove and
> return the head of the list stored in PLACE.", and I assume this is
> what CL `pop' is supposed to do.  Using it in that way in elisp should
> never generate a warning IMHO.

I agree that the warning is too pedantic.  But it's still true,
though.  The part to notice in the docstring is

   and return the head of the list
 
If we don't use the return value from pop, then

  (setq x (cdr x))

is obviously more efficient than 

  (pop x) == (car (prog1 x (setq x (cdr x))))



  reply	other threads:[~2003-04-28 22:30 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-27  4:48 Lars Magne Ingebrigtsen
2003-04-27  8:05 ` Romain FRANCOISE
2003-04-27  8:49   ` Florian Weimer
2003-04-27  8:53     ` Lars Magne Ingebrigtsen
2003-04-27  9:36       ` Romain FRANCOISE
2003-04-27 10:14         ` Lars Magne Ingebrigtsen
2003-04-28  7:42           ` Romain FRANCOISE
2003-05-01  6:27             ` Lars Magne Ingebrigtsen
2003-05-01  9:12               ` Romain FRANCOISE
2003-05-01  9:16                 ` Lars Magne Ingebrigtsen
2003-04-27  8:51   ` Lars Magne Ingebrigtsen
2003-04-27  9:37     ` Romain FRANCOISE
2003-04-27  8:59   ` Vasily Korytov
2003-04-27  9:33     ` Romain FRANCOISE
2003-04-27 11:07 ` Matthias Andree
2003-04-27 11:13   ` Lars Magne Ingebrigtsen
2003-04-27 11:14   ` Lars Magne Ingebrigtsen
2003-04-27 11:48     ` Florian Weimer
2003-04-27 11:55       ` Sebastian D.B. Krause
2003-04-27 12:30     ` Matthias Andree
2003-04-27 12:47       ` Romain FRANCOISE
2003-04-27 15:26         ` Simon Josefsson
2003-04-27 15:42           ` Romain FRANCOISE
2003-05-01  6:30             ` Lars Magne Ingebrigtsen
2003-05-01  9:10               ` Romain FRANCOISE
2003-05-01 12:39                 ` Simon Josefsson
2003-04-28 17:03           ` Jesper Harder
2003-04-28 19:10             ` Simon Josefsson
2003-04-28 22:30               ` Jesper Harder [this message]
2003-04-29  5:45                 ` Kevin Greiner
2003-05-01  6:27             ` Lars Magne Ingebrigtsen
2003-04-28 10:17 ` Christoph Garbers
2003-05-01  6:29   ` Lars Magne Ingebrigtsen
2003-05-01 11:16     ` In-Reply-To header (was: Oort Gnus v0.19 is released) Reiner Steib
2003-05-01 12:13       ` In-Reply-To header Lars Magne Ingebrigtsen
2003-05-04 19:37     ` Oort Gnus v0.19 is released Christoph Garbers
     [not found] ` <yaaptn8jfjf.fsf@fjorir.ifi.uio.no>
2003-05-01 13:25   ` Jan Egil Hagen
2003-05-02 16:08     ` Lars Magne Ingebrigtsen
2003-05-02 22:49       ` Jan Egil Hagen
2003-05-04 16:42         ` Lars Magne Ingebrigtsen

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=m3he8ib6g4.fsf@defun.localdomain \
    --to=harder@myrealbox.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.
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).