From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: [ELPA] Update package: psgml: handle (compile-internal) obsoletion
Date: Thu, 18 May 2017 09:04:22 -0400 [thread overview]
Message-ID: <jwvvaoyjpbu.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: m0shk2ime6.fsf@gmail.com
> It looks like (compile-internal) has been deleted, finally. This patch
> (see attached) adds a check to use the new (compilation-start) while
> still being compatible with really old versions.
Thanks, installed into elpa.git (but without the check: this version of
Psgml doesn't work in such old Emacs versions anyway).
> My computer ships with v22,
Well, personally, I don't consider that Emacs is distributed
with MacOSX. They include some crippled tty-only version of it,
probably for sysdmin purposes.
> I'm not very familiar with Emacs' dynamic loader. Does it optimize
> out the branch instruction on load since it's a comparison of a
> constant?
Actually, it's not a constant: it's a variable which will probably
never be modified.
> or does compiled code get interpreted literally?
It's pretty much interpreted literally.
> It's only a quick branch and calling the external procedure takes
> much longer, but I used the version check instead of (fboundp) since
> it's probably faster than the obarray lookup if the check is
> performed every time you call the procedure.
fboundp doesn't do an obarray lookup. It already has the symbol so it's
only an field access within the symbol object. It might very well be
faster than your < test (but I won't go and test it because I'm pretty
sure it's 100% lost in the noise, anyway).
Stefan
prev parent reply other threads:[~2017-05-18 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 8:45 [ELPA] Update package: psgml: handle (compile-internal) obsoletion Lucien Pullen
2017-05-18 13:04 ` Stefan Monnier [this message]
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=jwvvaoyjpbu.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
/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).