Re: Concurrency, again

[Tom Tromey]

>>>>> "Ken" == Ken Raeburn <address@hidden> writes:

Ken> In fact, in order to get a better
Ken> understanding of it, I set up a private repository where I broke up
Ken> the concurrency branch changes — not each commit, but the overall diff
Ken> from the branch point — into little pieces, separating straightforward
Ken> but pervasive changes from more subtle changes so I could figure out
Ken> what the latter were doing.  The result of my merge that I checked in
Ken> was in fact the result of rebasing those little changes onto the
Ken> latest master branch, fixing them up as necessary as I went along.
Ken> (But the resulting body of code was checked in as a merge commit so as
Ken> to preserve history of the work on the branch — what change was put
Ken> in, who fixed what bugs, etc; I wasn’t about to unilaterally throw
Ken> that away.  It was just a slow, tedious, manual merge process instead
Ken> of an automated one.)

Your branch sounds promising.

Ken>  * one thread per terminal?

This was something I thought would be useful, but not a must-have.

Tom