Alain Picard writes:
> I'm curious if anyone has played with trying to get ILU or
> a CORBA orb to work with clisp?
Marcus Daniels made some patches for getting ILU working in CLISP a few
years ago.
But, as you say it, the stumbling point is the need for multithreading:
connecting to CORBA implies listening on the ORB's socket and answering
when a request arrives. And at the same time, you also want to execute
your application. (At least, this is the stumbling point with ILU and
with MICO.)
Bruno

>>>>> "ap" == Alain Picard <alain.picard@...> writes:
ap> I've seen a project called CLORB on sourceforge, but it seems
ap> rather raw. ILU is quite mature, and could read CORBA interfaces,
ap> but does not seem to have been ported to clisp.
I can send you patches to make CLORB-0.1 work with CLISP-2000-03-06
(the client side, at least). I haven't tried ILU.
--
Eric Marsden <URL:http://www.laas.fr/~emarsden&gt;

I'm curious if anyone has played with trying to get ILU or
a CORBA orb to work with clisp?
I've seen a project called CLORB on sourceforge, but it seems
rather raw. ILU is quite mature, and could read CORBA interfaces,
but does not seem to have been ported to clisp.
Is anyone using clisp in that way? Or is everyone waiting for
multithreaded support before they attempt this?
--Alain Picard

Sam Steingold writes:
> Form: (PRIN1-TO-STRING *TERMINAL-IO*)
> CORRECT: "let's see what we get here"
> CLISP: "#<TWO-WAY-STREAM>"
Thanks. The correct fix will be to change the STREAM-ELEMENT-TYPE function
for two-way-streams and echo-streams to return a more restricted element type
than (OR CHARACTER INTEGER), if possible. That will also help the
READ-SEQUENCE and WRITE-SEQUENCE functions.
Bruno

Sam Steingold writes:
> but the above error is generated as a part of the build process (make
> check)
But I never got this error during "make check". So, what's wrong with
*terminal-io* ? Can you add a check for testing:
(prin1-to-string *terminal-io*)
"let's see what we get here"
?
Bruno

currently, clisp fails one test:
$ cat iofkts.erg
Form: (STREAM-ELEMENT-TYPE *TERMINAL-IO*)
CORRECT: CHARACTER
CLISP: (OR CHARACTER INTEGER)
$
while this is probably not too important, we should probably do somthing
about it. CLHS doesn't specify the element type for `*terminal-io*', so
why don't we just remove the test?
--
Sam Steingold (http://www.podval.org/~sds)
Micros**t is not the answer. Micros**t is a question, and the answer is Linux,
(http://www.linux.org) the choice of the GNU (http://www.gnu.org) generation.
Those who can't write, write manuals.

François Pinard wrote a week ago:
> In a word, Bruno says that CLISP does not use the Translation Project
> anymore, as he wants to format his POT files differently than we do.
>
> ... Probably that removing anything CLISP-related would be the
> most satisfying solution for everybody. Do you concur, Bruno? Upon a `yes',
> I'll just remove related POT and PO files, as well as registry entries.
Yes, I agree. I already proposed this a few months ago.
Thanks.
Bruno