Re: Re: RFC rampage
John DeSoi <[email protected]>
| Newsgroups | gmane.lisp.clump |
|---|---|
| Message-ID | <[email protected]> |
On Tuesday, June 10, 2003, at 04:23 PM, Erik Enge wrote:
> This sounds nice. What do you mean by processes? Threads? Forking?
> Do you know what implementations it will currently run on?
>
Here is what the mp package exports which should provide a general idea
on what it does:
current-process
interrrupt-process
lock
make-process
make-process-lock
process-add-run-reason
process-allow-schedule
process-kill
process-name
process-preset
process-property-list
process-revoke-run-reason
process-run-function
process-run-reasons
process-wait
with-process-lock
with-timeout
without-interrupts
without-scheduling
Current platforms for acl-compat (and Portable AllegroServe) include
LispWorks, CMUCL, OpenMCL, and MCL. I'm not sure of the implementation
status, but there are also folders in acl-compat for SBL, CLisp,
Corman, and SCL. And of course everything that uses acl-compat will
hopefully run on ACL :).
> There are a number of other aspects of the code which makes me not want
> to work with it, but these are more subjective opinions (if*, using
> comments instead of docstrings, etc).
I agree, some of it could be much better (I hate if*). But open source
gives you the option to improve rather than starting from scratch.
Best,
John DeSoi, Ph.D.