|Subject:||AW: console info|
|Date:||Sat, 8 May 2010 08:28:38 +0200|
I forgot to write that I will use Guile on a linux system.
Only the output “guile>” should be disable. All other outputs from Guile should go to the stdout.
A short overview:
I will write the output from Guile in variables. A second program communicates with the “Guile”-program over netcat. This program sends instructions to the Guile program. Then the Guile program returns some data (for example an integer). When I now write the output in the second program into a variable, I write also the “guile>” into it. Because of this I will only disable the output of “guile>”.
I hope I write this a little bit understandable. J
I'm messing around with MS Windows right now...
One interesting way is
"How to spawn console processes with redirected standard handles"
sample code at :
and it is quite a general solution for many applications (such as using guile with windows).
Having a console with windows is easy to do, and VERY useful for writing debug info using a simple printf(). (compile with a -mconsole flag).
You could hack around your guile source of course ;O).
Hope this helps,
From: Sven Schäfer
Sent: Friday, May 07, 2010 8:28 PM
Subject: (no subject)
I’m new in this list and I use Guile for the first time.
I start Guile in a program written in C.
Is it possible to disable the output “guile>” at the standard output?
That means, when I start Guile there is no “guile>” in the command line but I can give instructions to the interpreter.
I hope somebody can help me with this problem.
|[Prev in Thread]||Current Thread||[Next in Thread]|