Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.sys.apple2
Subject: Re: Applications: What you'd like to see
Message-ID: <14893@smoke.brl.mil>
Date: 17 Jan 91 23:50:13 GMT
References: <11145@ucrmath.ucr.edu> <14880@smoke.brl.mil> <1991Jan17.202210.26092@src.honeywell.com>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 17

In article <1991Jan17.202210.26092@src.honeywell.com> shankar@SRC.Honeywell.COM (Subash Shankar) writes:
>In article <14880@smoke.brl.mil> gwyn@smoke.brl.mil (Doug Gwyn) writes:
>>On my "to do" list is a port of the "sam" editor to the IIGS.  There are
>>a few serious obstacles to be overcome, though:
>>	1.  It runs as two processes, one to manage the files and one to
>>	manage the user interface.  These would have to be merged into a
>>	single coordinated process, not an easy job.
>I'm just saying that it might not be so hard to implement. 

Thanks for the suggestions.  Whatever solution I come up with would have
to be via portable C; I would incorporate this into the master BRL "sam"
sources that I maintain as a sort of distribution service to keep people
from pestering Rob too much about "sam".  (One needs an AT&T UNIX System
ToolChest "sam" license or else permission from Rob before I'll send the
sources.)  I'm pretty familiar with concurrent programming practicalities
and know what needs to be done here, but without a portable method of
implementing coroutines in portable C this IS a fairly difficult task.