Re: more fun with proposals

(no name) (Marc Snir/Watson/IBM Research@nas.nasa.gov)
10 Jul 96 14:28:59

The proposal of Salo is a restriction of my alternate proposal. I.e., my
alternate proposal allows to do what Eric proposes, and allows also some other
styles of programming. So why do we restrict?

1. Because it's simpler to explain. That's a weak argument: a textbook could
start with the simple rules in Eric's message and then go into more complex
mechanisms. If pushed, I am even willing to reorganize accordingly the draft.

2. Because it's simpler to implement. Somebody wants to make this case? I
think we still need the same machinery.

3. Because the restriction causes no loss of important function. But I
understand from the Cray people that (put/get, barrier)* style is quite
prevalent.

Comments?