unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Josep Portella Florit <jpf@primfilat.com>
To: Andy Wingo <wingo@pobox.com>
Cc: 20938@debbugs.gnu.org
Subject: bug#20938: make-dynamic-state, with-dynamic-state & exceptions
Date: Fri, 3 Mar 2017 23:15:42 +0100	[thread overview]
Message-ID: <b558d074-771e-16f2-c67a-42f2f20ef309@primfilat.com> (raw)
In-Reply-To: <87wpc8dhwe.fsf@pobox.com>

On 03/01/2017 06:30 PM, Andy Wingo wrote:
> On Wed 01 Mar 2017 16:11, Josep Portella Florit <jpf@primfilat.com> writes:
>> (Today I've tested it with 2.1.7.22-fcebf and it still crashed.)
> 
> Ack, I didn't actually test it!  I thought a related fix in 2.1.7 would
> have caught it.  I will have a look.

OK, can you reopen the bug?


>> BTW, did you change your mind on deprecating dynamic states?
>> <http://lists.gnu.org/archive/html/guile-devel/2016-06/msg00104.html>
> 
> Yes, with a caveat.  Having captured dynamic states also be mutable
> places was untenable, as you could have multiple threads mutating the
> same place at one time.  However dynamic states work well as a way to
> transport a parameterization from one part of the code to another.  I
> rely on them in Fibers for this purpose.  What do you think? :)

Your use of `current-dynamic-state` in Fibers confused me, until I
realized it works like `make-dynamic-state` in Guile 2.1.  Good, now
dynamic states are more analogous to Racket's parameterizations :-)





  reply	other threads:[~2017-03-03 22:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 13:50 bug#20938: make-dynamic-state, with-dynamic-state & exceptions Josep Portella Florit
2015-07-01  6:49 ` bug#20938: Improved workaround Josep Portella Florit
2016-03-13 14:57 ` bug#20938: More information Josep Portella Florit
2016-06-24  7:11 ` bug#20938: make-dynamic-state, with-dynamic-state & exceptions Andy Wingo
2016-06-24 14:58   ` Josep Portella Florit
2017-02-28 14:17 ` Andy Wingo
     [not found]   ` <1b66634b-9e69-da86-116a-088eafb383e7@primfilat.com>
2017-03-01 17:30     ` Andy Wingo
2017-03-03 22:15       ` Josep Portella Florit [this message]
2017-03-06 19:55         ` Andy Wingo
2017-03-07 20:36         ` Andy Wingo
2017-03-10 22:00           ` Josep Portella Florit

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/guile/

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

  git send-email \
    --in-reply-to=b558d074-771e-16f2-c67a-42f2f20ef309@primfilat.com \
    --to=jpf@primfilat.com \
    --cc=20938@debbugs.gnu.org \
    --cc=wingo@pobox.com \
    /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.
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).