At Wed, 20 Jul 2005 09:39:32 +0200,
felix winkelmann wrote:
> Absolutely. You can try out Thomas' suggestions. Alternatively, this is the
> code
> from srfi-18.scm, that makes the repl non-blocking:
>
> (set! ##sys#read-prompt-hook
> (let ([old ##sys#read-prompt-hook]
> [thread-yiel
Thomas and Felix, thank you for your suggestions.
I will check both of the methods, and see how it goes.
Daishi
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
On 7/19/05, Daishi Kato <[EMAIL PROTECTED]> wrote:
>
> Then, I would make a perl script to communicate with "my-http-server"
> and translate the S-expression command to any format,
> but the point is I would like to compile it.
>
> Does this make sense?
>
Absolutely. You can try out Thomas' sug
Hello,
why don't you just use (file-select ...) on the STDIN descriptor
(descriptor number 0) directly?
You could also cook up some code using fcntl to switch descriptor 0 into
non-blocking mode, checking for EWOULDBLOCK returns from read calls and
ensuring proper multithreading with the bui
At Tue, 19 Jul 2005 10:07:23 +0200,
felix winkelmann wrote:
>
> On 7/19/05, Daishi Kato <[EMAIL PROTECTED]> wrote:
> > For example, an application would be a server program
> > that is controlable by a user through some kind of commands.
> > In other words, a server program with CUI.
> > Currently
On 7/19/05, Daishi Kato <[EMAIL PROTECTED]> wrote:
> For example, an application would be a server program
> that is controlable by a user through some kind of commands.
> In other words, a server program with CUI.
> Currently I could do it by csi, since it does not block the server thread,
> but w
For example, an application would be a server program
that is controlable by a user through some kind of commands.
In other words, a server program with CUI.
Currently I could do it by csi, since it does not block the server thread,
but what if I would like to compile it into a single executable?
W
On 7/15/05, Daishi Kato <[EMAIL PROTECTED]> wrote:
> Hi,
>
> How could I make the standard (read) non-blocking?
>
Sorry, but currently I/O from stdio and files is fully blocking.
The reason why the REPL doesn't seem to block is due to a clever
hack (originally by Chris Double) that performs a se
Hi,
How could I make the standard (read) non-blocking?
I would like to get the following work.
Version 1, Build 941 - linux-unix-gnu-x86
(c)2000-2005 Felix L. Winkelmann
Using hygienic macros
; loading /usr/local/share/chicken/chicken-highlevel-macros.scm ...
#;1> (use srfi-18)
; loading library
