🚀 go-pugleaf

>X-Envelope-to: comp-windows-interviews@shelby.stanford.edu
>X-VMS-To: IN::"comp-windows-interviews@shelby.stanford.edu"

1
13-OCT-1992 18:53:06.75
   1 00:00:00.00
14-OCT-1992 18:53:06.75
daemon@interviews.Stanford.EDU
juando@cnm.us.es

Received: from interviews.Stanford.EDU by ESEVVX.CICA.ES ; 10-OCT-1992 18:53:01.29
Received: by interviews.Stanford.EDU (5.57/Ultrix3.0-C)
	id AA24473; Sat, 10 Oct 92 10:54:13 PDT
Received: by interviews.Stanford.EDU (5.57/Ultrix3.0-C)
	id AA23809; Sat, 10 Oct 92 10:49:35 PDT
Received: by lurch.Stanford.EDU (5.57/Ultrix2.4-C)
	id AA18826; Sat, 10 Oct 92 10:47:38 PDT
Received: by shelby.Stanford.EDU (5.57/Ultrix3.0-C)
	id AA16338; Sat, 10 Oct 92 10:43:53 -0700
Date: Sat, 10 Oct 1992 17:15:55 GMT
From: grunwald@foobar.cs.colorado.edu (Dirk Grunwald)
Organization: University of Colorado at Boulder
Subject: Re: Future support for threads?
Message-Id: <GRUNWALD.92Oct10111550@foobar.cs.colorado.edu>
References: <1992Oct8.160454.21211@leland.Stanford.EDU>
Sender: owner-comp-windows-interviews@shelby.stanford.edu
Reply-To: grunwald@foobar.cs.colorado.edu
To: comp-windows-interviews@shelby.stanford.edu

>>>>> On Thu, 8 Oct 92 16:04:54 GMT, denisb@leland.Stanford.EDU (Denis Bohm) said:
DB> Is there any future support for threads planned in InterViews?  It sure
DB> would make a number of things much easier to do...
--

Now that I can compile InterViews with g++, I was planning on doing
this using my thread library. I was basically going to have a thread
in the scheduler run the windowing event loop; however, since the
threads aren't premptive (for speed), it's not clear if this will
suffice. If anyone else wants to hack on this, you can get the thread
library Awesime:

	/anonymous@ftp.cs.colorado.edu:pub/cs/misc/Awesime

It works for mips-r[23]000, SPARC, m88k, i386, m68k and used to
support ns32k, but I haven't used that in a while.