Wow, don't know how I missed that one. Thanks AW! More code to learn
from. Good luck with lib choice Mike, I'll be watching and learning from
that as well.
-David
On Mar 3, 2017 1:35 AM, "Mike" wrote:
On Mar 3, 2017, at 01:24, David Bloom wrote:
Either of these two single header C librar
It needs clear:
o) you create demo picolisp code without native calls as demo and startpoint
o) I need a list of library functions you gonna use
o) I create native wrappers or something
o) you glue your code and native
On Thu, Mar 2, 2017 at 7:06 PM, Mike Pechkin wrote:
>
> hi,
>
> I need more e
> On Mar 3, 2017, at 01:24, David Bloom wrote:
>
> Either of these two single header C libraries is where I'm considering
> beginning my journey with native calls:
>
> nanomsg - a spiritual successor to ZeroMQ
> http://nanomsg.org/index.html
>
https://github.com/aw/picolisp-nanomsg
nano alr
Either of these two single header C libraries is where I'm considering
beginning my journey with native calls:
nanomsg - a spiritual successor to ZeroMQ
http://nanomsg.org/index.html
Or
nuklear - a slick looking, small ANSI-C GUI
https://github.com/vurtun/nuklear
I'm happy to pitch in code as
Graphviz!
> From: picolisp@software-lab.de On Behalf Of Mike Pechkin
> Subject: native calling
...
> I need more experience in (native) usage.
> If somebody need library bindings to something you can request here or
> directly.
...
PԔ � &j)mX�����zV�u�.n7�
I am not sure this sensible or even doable, but a binding to the torch
library (http://torch.ch) would be cool. Since Picolisp could use high
speed high dimensional math and machine learning.
It is written in C++ and already has a LUA interface. It needs a newer (< 4
years, i guess) NVIDIA graphics