Hi, to me there are (at least) two categories of JavaScript here that
need to be addressed. When I look at the page source for a Web app
(specifically, picolisp-gosper), I see two things:
(1) JavaScript which is loaded straight out of the files that come with
the release. As near as I can tell,
Mark Anderson
Principal Programmer, SIE Connected Content Group
**
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you
I see, 'later' itself sets up *Run.
Thanks Alex
On Wed, Mar 15, 2017 at 1:21 AM, Alexander Burger
wrote:
> Hi Bruno,
>
> > Joh-Tob's question got me curious about parallel code in picolisp. I've
> > studied the example of 'later' in the documentation and I have an idea of
I've completed this. I haven't yet contributed it to the todobackend.com
site. If someone wants to do that I'd be grateful
https://github.com/joebo/todo-backend-pil/
There are two versions - in-memory (non-persistent) and persistent using
the picolisp db. All tests are passing.
It was a fun
Hi Bruno,
> Joh-Tob's question got me curious about parallel code in picolisp. I've
> studied the example of 'later' in the documentation and I have an idea of
> how it works, but I don't understand how 'wait' works inside of it.
> I understand *what* it does, it makes sure that the child