Sorry friends, it was STILL not completely correct! :-(
On Mon, Oct 20, 2008 at 07:09:06AM +0200, Alexander Burger wrote:
Fixed! I uploaded a new testing version.
Both effects were a result of the fact that 'pipe' did not write to the
process' standard output as it should. Instead, it used
the problem be that xml is outputting unchunked to pipe and the
http server chokes on this?
/Henrik
--
UNSUBSCRIBE: mailto:[EMAIL PROTECTED]
On Sun, Oct 19, 2008 at 12:04:12PM +0200, Alexander Burger wrote:
Trying (trace 'pipe) in the server
Ah, this does not work. Only normal functions (that evaluate all their
arguments) can be traced. 'trace' is not intelligent enough to know how
built-in functions evaluate their arguments.
Hi Tomas,
'pipe' worked fine except when run in a server which returned NIL.
This would indeed be a bug in the PicoLisp kernel. Do you think you can
construct a simple, stand-alone example that demonstrates this effect?
Cheers,
- Alex
--
UNSUBSCRIBE: mailto:[EMAIL PROTECTED]
I'm trying to output a nested list to text, see the (trace 'pipe)
output I copy pasted.
Why do you think there might be a bug in the kernel? Obviously
everything is working fine when we work in a non server context and as
far as I know the http server is not a part of the kernel?
Note also that
in a server.
Also, when using pipe version, the http output is messed up...
Cheers,
Tomas
--
UNSUBSCRIBE: mailto:[EMAIL PROTECTED]
