newlispfanclub.alh.net

Many lisps are taking over clojure's threading macros in some shape. Picolisp has a special variable @ that holds the result of the last computation of some functions (like newlisp's $it ). and is one of them and it enables it to use it for threading. Would something like this be welcomed in newlisp...

Yeah, I just felt a bit of redundancy, ! is synchronous which means it calls fork, exec and wait (or something similar, not sure how system is coded exactly). Then we call another fork and wait. But as you said process could solve this, although that requires a command-string which means I either ha...

Yes, that pretty much does it, thanks! As a nitpick - is there no way to wait-pid for something that is forked only once? Looking at the sources ! uses system which is a fork+exec sh -c and you need to wrap that in another fork to get the pid. And why is the exit code shifted?

There are some minor inconsistencies in the docs, namely: the Cilk API part here http://www.newlisp.org/downloads/newlisp_manual.html#cilk says the commands are available on windows, whereas each function (spawn, sync and abort) state "The function {func} is not available on Windows". So which one i...

Looking at http://www.newlisp.org/downloads/newlisp_manual.html#processes I see there are several ways to start an external process, namely !, exec, process and spawn. So I thought let's write my typical toy tool - parallel git pull. It's a simple script that gets a set of root folders, looks for su...