all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Chong Yidong <cyd@gnu.org>,
	12215@debbugs.gnu.org, Dmitry Antipov <dmantipov@yandex.ru>
Subject: bug#12215: CSET is unnecessarily confusing
Date: Fri, 24 Aug 2012 11:27:02 -0600	[thread overview]
Message-ID: <87zk5kjj4p.fsf@fleche.redhat.com> (raw)
In-Reply-To: <5037B7A6.5030202@cs.ucla.edu> (Paul Eggert's message of "Fri, 24 Aug 2012 10:19:34 -0700")

>>>>> "Paul" == Paul Eggert <eggert@cs.ucla.edu> writes:

Paul> How exactly does that work?  I just now looked at the concurrency branch
Paul> and its BVAR is the same as in the trunk.

Paul> Is BVAR a speculative change, that was put in because eventually we
Paul> thought we'd need it for concurrency?  If so, perhaps we should revert
Paul> it until the need is demonstrated.  After all, it's been many months
Paul> since BVAR went in, and the concurrency branch still isn't really
Paul> using it.

Yeah.

Originally I had planned a somewhat complicated scheme for handling
per-thread let bindings.  This scheme required some changes like BVAR.
I lobbied to get these changes into the trunk because carrying big
changes like this on a branch makes merging very hard -- this is partly
what sunk the first concurrency branch.

My planned bindings approach was tricky, though, and due to unrelated
changes in my life, I no longer have the time or energy to think through
all the details to make them work with other changes that have happened
in Emacs since then.  So on the new concurrency branch I opted for a
much simpler approach (which may still be wrong :-).

BVAR isn't needed right now.  It may be if someone else resurrects the
other approach.  It's unlikely I ever will.

Tom





  reply	other threads:[~2012-08-24 17:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17  0:04 bug#12215: CSET is unnecessarily confusing Paul Eggert
2012-08-17  4:12 ` Dmitry Antipov
2012-08-21 16:55 ` Stefan Monnier
2012-08-22  3:25   ` Paul Eggert
2012-08-22 13:27     ` Stefan Monnier
2012-08-22 16:35       ` Paul Eggert
2012-08-22 16:50         ` Dmitry Antipov
2012-08-23  7:02           ` Paul Eggert
2012-08-23 12:26         ` Stefan Monnier
2012-08-23 14:40           ` Paul Eggert
2012-08-24  3:46           ` Chong Yidong
2012-08-24  3:57             ` Paul Eggert
2012-08-24  4:26               ` Dmitry Antipov
2012-08-24 15:10             ` Stefan Monnier
2012-08-24 17:19               ` Paul Eggert
2012-08-24 17:27                 ` Tom Tromey [this message]
2012-08-24 18:11                   ` Paul Eggert
2012-08-24 21:12                     ` Stefan Monnier
2012-08-25  0:17                       ` Paul Eggert
2012-08-25  1:58                         ` Stefan Monnier
2012-08-26  5:05                           ` Paul Eggert
2012-08-21 17:55 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zk5kjj4p.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=12215@debbugs.gnu.org \
    --cc=cyd@gnu.org \
    --cc=dmantipov@yandex.ru \
    --cc=eggert@cs.ucla.edu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.