unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Miles Bader <miles@gnu.org>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: "simplifications"
Date: Mon, 19 Nov 2007 12:57:29 +0100	[thread overview]
Message-ID: <861wam1m8m.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <buohcjiwjtw.fsf@dhapc248.dev.necel.com> (Miles Bader's message of "Mon\, 19 Nov 2007 20\:33\:47 +0900")

Miles Bader <miles.bader@necel.com> writes:

> David Kastrup <dak@gnu.org> writes:
>> Personally, I think that we should make the byte compiler optimize the
>> unnecessary binding away.
>
> It'd be nice if it did, though you need to analyze the function to make
> sure there are no hidden uses of that binding; in particular, you need
> to know if any functions called inside the defsubst might use the
> dynamic binding of the defsubst's args.
>
> [I personally think that's a bit silly, and that it would be enough to
> just define defsubst as not guaranteeing dynamic bindings of its args,
> but as a recall, this has been discussed before, and the current
> behavior declared necessary...]

My recollection was rather that optimizing such cases (for a suitable
definition of "such") was deemed a good idea, but too invasive for the
Emacs 22 release schedule.

-- 
David Kastrup

  reply	other threads:[~2007-11-19 11:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 10:46 "simplifications" David Kastrup
2007-11-19 10:56 ` "simplifications" Juanma Barranquero
2007-11-19 15:11   ` "simplifications" Stefan Monnier
2007-11-19 15:19     ` "simplifications" David Kastrup
2007-11-19 15:39     ` "simplifications" Juanma Barranquero
2007-11-19 15:44       ` "simplifications" Stefan Monnier
2007-11-19 15:47         ` "simplifications" Juanma Barranquero
2007-11-19 15:58           ` "simplifications" Stefan Monnier
2007-11-19 16:08             ` "simplifications" Juanma Barranquero
2007-11-19 18:46               ` "simplifications" Stefan Monnier
2007-11-19 16:02         ` "simplifications" David Kastrup
2007-11-19 16:05           ` "simplifications" Juanma Barranquero
2007-11-20  3:59         ` "simplifications" Richard Stallman
2007-11-20 15:27           ` "simplifications" Stefan Monnier
2007-11-21 21:37             ` "simplifications" Stephen J. Turnbull
2007-11-21 21:52               ` "simplifications" David Kastrup
2007-11-22  1:34                 ` "simplifications" Stephen J. Turnbull
2007-11-19 11:02 ` "simplifications" Juanma Barranquero
2007-11-19 11:33 ` "simplifications" Miles Bader
2007-11-19 11:57   ` David Kastrup [this message]
2007-11-19 12:08     ` "simplifications" Juanma Barranquero
2007-11-19 12:21       ` "simplifications" David Kastrup
2007-11-19 12:32         ` "simplifications" Juanma Barranquero
2007-11-19 12:49           ` "simplifications" David Kastrup
2007-11-19 12:54             ` "simplifications" Juanma Barranquero
2007-11-20  3:59 ` "simplifications" 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=861wam1m8m.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=miles@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).