Re: small patch to get scsh running
Roderic Morris <[email protected]> Thu, 22 Apr 2010 09:37:49 -0700
| Newsgroups | gmane.lisp.scheme.scheme48 |
|---|---|
| Message-ID | <[email protected]> |
> - I see you took the 0.6 scsh packages, which have all the scsh code in > one huge structure. Did you look at the trunk on SourceForge, where > it's broken up in multiple structures? No, I didn't even think of looking in that repo honestly. Wish I had though, that would've been useful and so much easier to understand. Gonna try to integrate that change (and any other useful ones I can find in there) with what I have now. > - What are your thoughts on dealing with the threads-narrowing issue? I've been avoiding threading issues altogether honestly. I just wanted to get the code to a point where it could run on a vanilla s48 vm. And, I've been too busy lately to go much further. Thinking about it now though, it seems like narrowing is the right way to go, but I don't want to have to fork s48 to do it. The implementation in 0.6 required adding a new event type and maybe some other things I wouldn't be able to do with just the threads-internal package. > - What are your thoughs on implementing `select' & friends? I haven't thought about it much yet. I'd like to do that if they aren't already there (isn't select implemented?), especially epoll to write something like tornado <http://tornadoweb.org> in scsh. I've been focusing on fixing breakage though, which there's still a lot of. > - I saw this in thread-fluid.scm: > > ;;; because I'd like to have scsh stop using thread-fluids altogether if I can > ;;; later. > > I'd be curious about your thoughts on this. (Of course, the obvious > way to get rid of them is to clean up the scsh API - an option that > wasn't available to us at the time.) That file was written early on, before I spoke to you about them. I'm going to reevaluate that once I get to seriously thinking about how to handle threads of course. > Also, you might want to send your announcement to the scsh mailing list > as well ... Yes, someone's suggested that. I've been reluctant though, since it's still pretty broken. At this point though, since I can't devote much time to it for now, and the instructions for setting it up are a bit simpler with that patch in, I'll announce it soon. -Roderic