[e-lang] Content Complete, Ready for Comments

[David Hopwood]

Mark Miller wrote:
> At <http://www.erights.org/talks/promises/paper/index.html> is a 
> content-complete draft of the TGC paper.

Here are some trivial grammar nits and typos:

# By contrast, when writing a program, we must express a plan that can
# deal with all possible relevant contingencies.

"all relevant" or "all possible and relevant".

# The style recommended by some rendezvous-based languages

"recommended for"

# This is ''Multi-Threaded Hell''.

Use `` for opening quote.

# As your application evolves, or as different programmers encounter the
# sporadic and non-reproduceable corruption or deadlock bugs,

"non-reproducible"
(Yes, it's a quotation, but this should be silently corrected.)

# However, this style still suffers from the same race conditions hazard,
# and so still fails to exclude enough interleavings.

"race condition hazards"

# >From a lambda calculus perspective,

Delete ">".

# There are formal models of asynchronous systems which can account for
# non-terminating events [7].

"that can account"
("can account for non-terminating events" is a restriction on the models
being referenced, rather than an incidental observation about the models.)

# But it is not P’s responsibility to worry about Q’s behavior outside
# those limits; it is R’s responsibility to prevent those.

"prevent it"
("Q's behavior outside those limits" is an 'it', not a 'those'.)

# Like non-signaling NaNs, broken promise contagion does not hinder pipelining.
# Both suppress only data dependent computation, but with a difference.
#
# A non-signaling NaN is contagious if used in any argument position.

Suggest moving the paragraph break to before "Like non-signalling..."

# A sturdy references is a form of off-line "password" capability

"reference"

# To establish or re-establish access to the target, one makes a new live
# reference from a sturdy reference. [...]
# As part of this respawning process, the two sides may need to reconcile --
# to restablish distributed consistency.

"reestablish"

# When reconciling, it should navigate afresh, in order to find the statusHolders
# is now need to subscribe to.

"it now needs"

# Once one makes a sturdy reference to a given object, it's hosting vat can no
# longer determine when its unreachable.

"its hosting vat can no longer determine when it is [or it's] unreachable".

# Distributed Shared Memory systems (DSMs) [NL91] tries to make the network
# seem more like a von Neumann machine.

"try to"

# Instead of dividing ''computer stuff''

Use ``.

# we independently reinvented an assymmetric form of promise pipelining as
# part of our protocol design.

"asymmetric". Also need a reference, possibly
<http://www.sunless-sea.net/Transcripts/promise.html>?

# Notice that all the examples presented in this paper happen to work when
# all the objects involved happen to be local.

"are local"

# [zBDMS98] &#214;zalp Babao&#287;lu,

\"{O}zalp Babao\u{g}lu

-- 
David Hopwood <david.nospam.hopwood at blueyonder.co.uk>