Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!texbell!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.tech Subject: Re: SKsh 1.5 release available Message-ID: <6086@sugar.hackercorp.com> Date: 24 Jul 90 11:03:45 GMT References: <13920076@hpfelg.HP.COM> <13920077@hpfelg.HP.COM> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 24 In article <13920077@hpfelg.HP.COM> koren@hpfelg.HP.COM (Steve Koren) writes: > 2) I would like to hear any ideas for possible extensions to > the ARexx port. I think you should probably run the arexx port in a child process. That's what we do with TCL: for any given TCLish program, we run two copies. One is used interactively and the other is purely a batch processor. To get information back to the main one we have it send a message to the batch guy. Much better than pretending to be a Mac program and busy-waiting. Interaction between asynchronous command processors is a complex subject, but by and large any given O/S level thread should only have one control flow. Particularly is the alternative is busy-waiting. > Lastly, besides "real" pipes, are there still significant features > that people want which aren't in SKsh? Do you have "here documents" yet? "setmap" is a poor name, since that's an Amiga program to set the keyboard mapping. -- Peter da Silva. `-_-' .