Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@iskon.hr>
Subject: Re: CVS: Symbol's function definition is void: ignore-errors
Date: 04 Dec 1999 21:10:11 +0100	[thread overview]
Message-ID: <9t9wvqu8o2k.fsf@mraz.iskon.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "04 Dec 1999 20:58:14 +0100"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> > b) Some of them carry interesting meta-information that is not easy to
> >    transfer, such as instructions for byte-optimizer.  cl.el is
> >    smarter than it appears -- some of the seemingly cluttered function
> >    and macro constructs compile to efficient byte-code.  (See the
> >    various compiler macro definitions in cl-macs.el)
> 
> Yup.  That's why I want the byte-code, not the functions themselves.

But the byte-code doesn't have the whole info.  My point is that, for
instance:

(disassemble
  (lambda () (eql x 'bar)))

...disassembles to code that uses `eq' because it's safe.  OTOH, this:

(disassemble
  (lambda () (eql x y)))

...disassembles to code that uses `equal', because EQUAL has its own
byte-code instruction, and it's faster than calling `eql'.

If you do something like (fset 'gnus-eql (indirect-function 'eql)),
you lose this meta-information.  This is a trivial example, but there
are more.

EQL is a trivial example, but there is more where that came from.
"compiler macros" != "Lisp macros".

> #[(cl-seq &rest cl-keys) "byte code removed" [cl-delete-duplicates cl-seq cl-keys nil] 4 596479]
> 
> Er.  But the cl functions call other cl functions.  Er.  Uhm.  Hm.
> Can I alter the contents of the byte-compiled function to call the
> Gnus functions instead?  My, this is getting rather complicated...

Yup.

> > Maybe it would be a better approach to really really beg Stallman
> > to allow Gnus to use the nice CL thingies.  Gnus is *huge*.  I
> > don't think anyone will notice the difference.
> 
> I think it's mainly a name-pollution thing for RMS.  Having
> `delete-duplicates' in the namespace will make people believe that's
> a proper Emacs function and stuff.

Isn't it, really?  It ships with Emacs, it's GPL-ed, it's assigned to
the FSF, it works nicely, it sings and it cooks for you.  If noone is
supposed to use it, why is it there in the first place?


  reply	other threads:[~1999-12-04 20:10 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-04 11:42 Thomas Skogestad
1999-12-04 13:11 ` Raymond Scholz
1999-12-04 16:51   ` Andi Hechtbauer
1999-12-04 16:52 ` Michael Welsh Duggan
1999-12-04 17:00   ` Andi Hechtbauer
1999-12-04 17:11     ` Shenghuo ZHU
1999-12-04 17:45       ` Per Abrahamsen
1999-12-07  4:39         ` Emerick Rogul
1999-12-07 10:43           ` Per Abrahamsen
1999-12-07 12:19           ` Thomas Skogestad
1999-12-07 12:46             ` Per Abrahamsen
1999-12-07 14:22               ` Raymond Scholz
1999-12-07 14:38                 ` Per Abrahamsen
1999-12-07 16:07                   ` Emerick Rogul
1999-12-07 14:51           ` Dave Love
1999-12-04 17:11     ` Michael Welsh Duggan
1999-12-04 17:57 ` Dave Love
1999-12-04 18:21   ` Hrvoje Niksic
1999-12-04 19:31     ` Lars Magne Ingebrigtsen
1999-12-04 19:42       ` Lars Magne Ingebrigtsen
1999-12-06 14:03         ` Andreas Schwab
1999-12-04 19:44       ` Hrvoje Niksic
1999-12-04 19:58         ` Lars Magne Ingebrigtsen
1999-12-04 20:10           ` Hrvoje Niksic [this message]
1999-12-04 20:36             ` Lars Magne Ingebrigtsen
1999-12-04 20:53               ` Hrvoje Niksic
1999-12-05 23:11           ` Kai Großjohann
1999-12-05  0:11         ` Dave Love
1999-12-05  0:06     ` Dave Love
1999-12-07 23:42     ` Eric Marsden
1999-12-07 23:50       ` David Maslen
1999-12-08  9:23       ` Hrvoje Niksic

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=9t9wvqu8o2k.fsf@mraz.iskon.hr \
    --to=hniksic@iskon.hr \
    /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).