From: Paul Pogonyshev <pogonyshev@gmx.net>
Cc: emacs-devel@gnu.org, rms@gnu.org,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: byte-code optimizations
Date: Wed, 22 Sep 2004 01:31:59 -0200 [thread overview]
Message-ID: <200409220131.59482.pogonyshev@gmx.net> (raw)
In-Reply-To: <20040921211527.GA3394@fencepost>
> On Tue, Sep 21, 2004 at 05:05:30PM -0400, Stefan Monnier wrote:
> > What defsubst* does is treat the argument as a kind of "lexically scoped"
> > variable, but only in very limited ways. I.e. the
>
> ...
>
> > (defsubst* foo (x) (symbol-value x))
> >
> > (foo y) => (symbol-value y)
> >
> > whereas our optimization won't be able to do that because it can't assume
> > a "somewhat lexically scoped" semantics.
>
> I vote for saying "you're not allowed to treat defsubst argument bindings
> as normal dynamic bindings, and if you have tons of code that does, well
> screw you, you're probably a crappy programmer anyway."
While I do agree with this, it's generally better to avoid changing
stabilized behaviour only for optimization reasons. Otherwise,
really-difficult-to-debug bugs can jump out of nowhere.
Paul
next prev parent reply other threads:[~2004-09-22 3:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-18 13:52 byte-code optimizations Paul Pogonyshev
2004-09-18 20:26 ` Stefan
2004-09-19 11:00 ` Richard Stallman
2004-09-19 16:15 ` Paul Pogonyshev
2004-09-21 18:31 ` Richard Stallman
2004-09-22 0:42 ` Paul Pogonyshev
2004-09-21 21:05 ` Stefan Monnier
2004-09-21 21:15 ` Miles Bader
2004-09-22 3:31 ` Paul Pogonyshev [this message]
2004-09-21 22:57 ` Miles Bader
2004-09-22 3:25 ` Paul Pogonyshev
2004-09-22 18:20 ` Richard Stallman
2004-09-23 0:33 ` Paul Pogonyshev
2004-09-18 22:55 ` 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=200409220131.59482.pogonyshev@gmx.net \
--to=pogonyshev@gmx.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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).