volatiles

[David Collier-Brown]

| In article <1414 at pt.cs.cmu.edu> edw at IUS1.CS.CMU.EDU (Eddie Wyatt) writes:
||     Another option for you is to consider developing an entire new
|| language with multi-tasking support.  Design it in such way that it
|| is easy to optimize, and is general enough to describe external events
|| such as hardware as a special task.

   Ok, see below...

In article <4437 at ihlpf.ATT.COM> nevin1 at ihlpf.UUCP (00704a-Liber,N.J.) writes:
| Do you intend to rewrite all of Unix and all the C applications currently
| in use in your new language?  And are you willing to train all the people
| who are going to use this new language?  And what do we do during the three
| or four years that it is going to take to fully develop this language?
| Writing an entirely new language is not a viable solution for the short
| term.

   Short term?  The short term is **always** already over.  

   The language has existed for a number of years, was announced in
a special issue of Software, Practice and Experience, has a small
but vocal programmer base, is used in several Universitys to teach
Operating Systems and is even available on an IBM Poisonous Computer...

  Per Brinch Hansen's "Edison":

  while (not done)
	outputBuffer = inputBuffer;
	cobegin 1
		fill(inputBuffer,stream1);
	and 2
		empty(outputBuffer,stream2);
	coend
  end while

--dave (minor syntactics errors admitted) c-b
-- 
 David Collier-Brown.                 {mnetor yunexus utgpu}!geac!daveb
 Geac Computers International Inc.,   |  Computer Science loses its
 350 Steelcase Road,Markham, Ontario, |  memory (if not its mind) 
 CANADA, L3R 1B3 (416) 475-0525 x3279 |  every 6 months.