Points for Chapter 6 (evaluation)
=================================

-01	FT-Linda's AGS is novel: nobody else provides anything
	with multi-op atomicity that has less than transactions.

-02	Other FT-Linda features are novel:
		- multiple TSs (esp w/attributes)
		- disjunction
		- strong semantics (MOM had oldest matching,
				though ours was in place by then)
		

-03 	FT-Linda is general: it can implement the 3 major
	ftol structuring paradigms, plus many ones for
	scientific/parallel programming paradigms

-04	RELATED WORK (look at TPDS summary and expand?)

-05	Coherence of Language Design

		- multiple TSs natural extensions
		-  TS attributes orthogonal and combined intuitively
		-  AGS restrictions clean and clear
		- tuple transfer primitives clean and clear
		- disjunction intuitive

-06	Explain AGS restrictions clearly, explain
	slippery slope if start allowing expressions and
	functions and conditional statements, etc.
	
	Could mention that Orca's operation guards have to
	be side-effect free, so operations only block
	before they begin execution.  This is important,
	since operations must execute atomically.  
	Dave see Coffin diss. p. 169 for a discussion of this.

	Could explain how the blocking restriction lets you avoid
	worring about concurrency and rolling back TS ops
	in the event of a failure.  Dennis Shasha thought
	that one very nice feature of FT-Linda was that
	there was no concurrency in the RTS.

-07 	Could mention that we could allow non-Linda guards
	using variables.  This could even be combined with
	a Linda op, e.g.

		bool flag = ....	
		< not flag and not inp(foo...) => ... >

	MAYBE THIS SHOULD GO IN SEC 3.4???!!!

-08	Paths not taken

-09	Observed deficiencies

-10	Comparing FT-Linda and transactional Lindas

-11	Add any other ideas from TICS chart