Re: [dylan] Stream locking (was: Method combinations as a design pattern for locking)
Bruce Mitchener <[email protected]> Wed, 18 Dec 2013 16:43:26 +0700
| Newsgroups | gmane.comp.lang.dylan.gwydion.devel |
|---|---|
| Message-ID | <CA+esKjOuZmbuFnEBeatLPGE61L9ftdNZPsa0br1idn4XeRbhGg@mail.gmail.com> |
On Wed, Dec 18, 2013 at 12:17 PM, Bruce Mitchener <[email protected] > wrote: > On Wed, Dec 18, 2013 at 9:30 AM, Bruce Mitchener < > [email protected]> wrote: > >> I think the key steps to moving forward with this are: >> >> >> - Try to identify why this change to stream locking was made in the >> first place and what changes will have to be made to applications as a >> result of this change. (Given that it was Hannes and Andreas, I'm assuming >> it was either DUIM/Gtk+ or Network Night Vision.) >> - Make the changes for the 2014.1 release and make sure that we >> explain them clearly. >> >> I think that having locking in format-out and force-out will be >> sufficient for many people. >> > > No updates to documentation or release notes yet, but perhaps this can go > into 2013.2: > > https://github.com/dylan-lang/opendylan/compare/stream-locking-changes > > I have a 3 stage bootstrap in progress with these changes, but I don't > expect issues since dylan-compiler is single-threaded. > A couple of fixes later, added release notes and so on... Pull request: https://github.com/dylan-lang/opendylan/pull/621 I ran the sample code from bug 4004 in Bugzilla and it is fine now. Anyone want to pull the trigger and merge it? - Bruce _______________________________________________ hackers mailing list [email protected] https://lists.opendylan.org/mailman/listinfo/hackers