From: Rich Lane <rlane@club.cc.cmu.edu>
To: Edward Z. Yang <ezyang@mit.edu>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Strategy for dealing with nil and thread errors
Date: Fri, 21 Jan 2011 01:46:53 -0500 [thread overview]
Message-ID: <1295572751-sup-2112@zyrg.net> (raw)
In-Reply-To: <1295563880-sup-5855@ezyang>
I think the UI should be single-threaded and event-driven. Index and
source operations should still be run in separate threads or processes
to avoid freezing the UI, but they should not be sharing any mutable
state.
This is a lot of work. If anyone is interested in tackling this I
suggest first discovering all the threads Sup uses and which of their
codepaths call into the UI or modify shared datastructures (Message,
Thread, ThreadSet, ...). Then that racy code needs to be moved to a
callback that runs in the event loop.
Some other robustness thoughts I've had:
- Immutable messages / different classes for messages constructed from
source vs index
- Catch and log exceptions from keybindings
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-01-21 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 22:57 Edward Z. Yang
2011-01-21 6:46 ` Rich Lane [this message]
2011-01-21 6:59 ` Tero Tilus
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=1295572751-sup-2112@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=ezyang@mit.edu \
--cc=sup-devel@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox