Thanks for the clarification!
Oh I absolutely love implementing protocols "just for fun", can't blame you for
that haha.
Please publish your code when it's ready, I'd love to have a look and lend
a hand if needed.
Cheers,
AW
--
UNSUBSCRIBE:
Hi Todd,
If you're calling out to ncat/socat, then it won't be a "pure" PicoLisp
client.
In that case, why not simply call out to an existing C client or
library such as Mosquitto: https://mosquitto.org/ ?
I've been doing that since ~2016 by calling the mosquitto_pub client from
PicoLisp
Hello everyone and Happy New Year!
I've recently updated the PicoLisp "GitHub Action" to help build/test
applications automatically with pil21:
https://github.com/marketplace/actions/picolisp-action
The latest is v3, which completely removes support for 32-bit picolisp, and
other 64-bit
Hi,
I wrote some code examples for interfacing Zig lang with PicoLisp using
(native). You can see it here:
https://github.com/aw/picolisp-zig
It is almost identical to my picolisp-rust project
(https://github.com/aw/picolisp-rust), so it might be familiar to some.
Zig is nice and easy, a
Hi Jason,
I don't want to be rude, but to put emphasis on what Alexander Burger
wrote, your code is really bad. It doesn't follow any of the very simple
"naming conventions" of PicoLisp, and it doesn't even follow other
LISP "coding conventions". It's hard to read, difficult to grok, messy,
Try:
(setq *Str (in '(/bin/ls) (till NIL T)))
Each entry will be separated by a newline "^J"
There are other ways to do this...
AW
On Thu, 25 Apr 2024, Patrick Lebas wrote:
How can I get the Stream-out from
(call 'ls) and put it into a string (setq str...) ? THANKS.
Envoyé à partir de
