On Fri, Oct 09, 2009 at 08:59:43PM +0200, Tomas Hlavaty wrote:
The (traditional) multiprocessing by forking, shared memory etc. is
error-prone and not scalable!
Do you have anything to support this assertion? I would rather disagree
on this. It is more reliable than using threads and
Hi Nik,
I had the intention to learn more about how the concurrency model
in PicoLisp compares to languages like Erlang, Termite (Gambit),
Clojure, Scala etc.
OK, I see ;-)
This is not well documented yet. The basic model (for the processes on a
single machine and operating on the same
Hi Nik,
I didn't find anything useful about multithreading and
concurrency model in PicoLisp by a quick search in google.
Does PicoLisp has some sort of built-in concurrency at all?
picolisp doesn't do threads but uses processes and ipc instead (see
'fork', 'pipe', 'tell', 'hear', 'rpc' etc.
--- On Fri, 10/9/09, Tomas Hlavaty t...@logand.com wrote:=0A How many pro=
cesses do you need?=A0 I can fork about 500=0A from one parent=0A (limite=
d by my OS set up).=A0 And because picolisp is,=0A well, pico, it=0A do=
esn't take much memory (picolisp uses less that 2MB).=0A=0AAnd if picolisp
