unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Daniel Colascione <dancol@dancol.org>,
	Emacs discussions <emacs-devel@gnu.org>
Subject: Re: [PATCH 06/10] add most lisp-level features
Date: Mon, 13 Aug 2012 15:02:08 -0600	[thread overview]
Message-ID: <87mx1y4ib3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <jwvpq6uwmp7.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 13 Aug 2012 16:46:54 -0400")

I'm not really trying to continue this sub-thread more than it needs to
be...

Tom> Yet one more observation here.  The Bordeaux approach lets you specify
Tom> which bindings to capture.

Stefan> AFAIK, you can easily do that manually with the "no capture" behavior
Stefan> as well.

All I could think of is backquote, which seems pretty gross.

  (make-thread
    `(lambda ()
       (let ((default-directory ,default-directory))
         ...)))

I'm not really a fan of the Bordeaux approach either though.
Better to have a convenience macro, I think.

Tom> Maybe everything important really will use lexical binding.

Stefan> At least the `make-thread' code will likely be in a lexical-binding
Stefan> file, yes.

It occurs to me now that even lexically bound code will use some
variables which are always dynamic.  It still seems odd not to capture
these.

Tom



  reply	other threads:[~2012-08-13 21:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 19:41 [PATCH 06/10] add most lisp-level features Tom Tromey
2012-08-10  1:45 ` Daniel Colascione
2012-08-13 14:51   ` Tom Tromey
2012-08-13 20:46     ` Stefan Monnier
2012-08-13 21:02       ` Tom Tromey [this message]
2012-08-14  1:13         ` Stefan Monnier
2012-08-14 14:46           ` Tom Tromey
2012-08-14 15:05             ` Stefan Monnier

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=87mx1y4ib3.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=dancol@dancol.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).