scsh-users
[Top] [All Lists]

Re: fork vs. spawn

To: scsh@martigny.ai.mit.edu
Subject: Re: fork vs. spawn
From: sjenkins@iastate.edu (Steven L Jenkins)
Date: 9 Aug 1996 14:27:47 GMT
Organization: Iowa State University, Ames, Iowa USA
In article <4ue1ja$t0o@roar.cs.utexas.edu>,
Paul Wilson <wilson@cs.utexas.edu> wrote:
>In article <xoirapibbzi.fsf@chops.icp.net>,
>Sean Doran  <smd@chops.icp.net> wrote:
>>-----BEGIN PGP SIGNED MESSAGE-----
>>
>>wilson@cs.utexas.edu (Paul Wilson) writes:
>>
...
>
>I realize that scsh's primary goal (at least right now) is to
>be a good scripting language for UNIX.
>
>I was trying to suggest a small concession to other OS's which
>didn't seem damaging to scsh-on-UNIX.

And I believe Olin wants to see scsh on other platforms (at least, he's
mentioned it to me before..)

...

>Having a very portable subset of scsh (that works on non-UNIX)
>seems generally desirable.  I'd also like to support full-blown
>scsh on UNIX.
>
>What I was trying to establish was whether it would be *difficult*
>to support a basic subset scsh on other platforms than UNIX.
>I am not asking anybody to commit much effort to it.  If it's
>pretty trivial, I might suggest it, or we might hack it when
>we get around to scsh support.
>
>>It may be that that kind of full-blown, portable
>>development environment would ultimately be more useful
>>to many people for many things, but "it's not UNIX".
>
>That's okay by me.  I understand the goal of making a full-power
>UNIX programming environment.  But does that exclude the
>possibility of a useful portable subset?

I've done some thinking/looking around for a port to the MS Windows
environment (3.X, 95, and NT), and, to be honest, I don't have
a clue what scsh would look like on those.  For a port to
NT, one could use the POSIX mode, but that eliminates using other
features of NT, but at least something could be done.  For the
other two, all I could think of would be providing the Windows API
in Scheme -- what's the win (no pun intended) there?  Perhaps those
needing/wanting to do Windows programming would find that useful?  
Such a system could be rather elegant, I'm sure (as compared to, say,
MFC or OWL).  I would envision it as something like a Visual Basic
competitor, but at that point, it seems to be getting quite far from
scsh and becomes another beast altogether.

FWIW, one of my goals is to have scsh available on several Scheme
platforms. 


<Prev in Thread] Current Thread [Next in Thread>