Subscribe

2015-03-03 Thread Alexander Williams

A PicoLisp native library tutorial

2015-03-03 Thread Alexander Williams
Hi list, Some of you might know me from IRC @aw-Unscramble. I've written my first PicoLisp library, a native C binding for Nanomsg (picolisp-nanomsg) - as an experiment for myself to learn this language. In doing so, I ran into a few difficulties (mostly noob stuff) but Regenaxer has been very h

Re: A PicoLisp native library tutorial

2015-03-03 Thread Henrik Sarvell
Nice! On Tue, Mar 3, 2015 at 5:36 PM, Alexander Williams wrote: > Hi list, > > Some of you might know me from IRC @aw-Unscramble. > > I've written my first PicoLisp library, a native C binding for Nanomsg > (picolisp-nanomsg) - as an experiment for myself to learn this language. > > In doing so,

Re: A PicoLisp native library tutorial

2015-03-03 Thread Joe Bogner
Nicely done. Thanks for sharing On Tue, Mar 3, 2015 at 12:16 PM, Henrik Sarvell wrote: > Nice! > > On Tue, Mar 3, 2015 at 5:36 PM, Alexander Williams > wrote: > > Hi list, > > > > Some of you might know me from IRC @aw-Unscramble. > > > > I've written my first PicoLisp library, a native C bindi

RE: A PicoLisp native library tutorial

2015-03-03 Thread Loyall, David
> From: Alexander Williams [...] > I also wrote a tutorial explaining the code, to help other > newbies understand some useful features of PicoLisp: > > https://github.com/aw/picolisp-nanomsg/blob/master/EXPLAIN.md This is great, Alexander! I really like this part: > (setq Result (12 104

Re: A PicoLisp native library tutorial

2015-03-03 Thread Jakob Eriksson
Yep. Definitely interesting. On 03/03/15 18:50, Joe Bogner wrote: > Nicely done. Thanks for sharing > > On Tue, Mar 3, 2015 at 12:16 PM, Henrik Sarvell wrote: > >> Nice! >> >> On Tue, Mar 3, 2015 at 5:36 PM, Alexander Williams >> wrote: >>> Hi list, >>> >>> Some of you might know me from IRC

Solaris 10 picolisp 64 build

2015-03-03 Thread Rick Hanson
Sorry in advance if you’ve already covered this issue in the past. I’m on Solaris 10; I can build the 32-bit picolisp (3.1.9) with no problem. Then, I go do a (cd src64; make) (which is GNU make btw); this builds the x86-64.sunOS.base.s file via mkAsm, but it fails in the next step on gas --64 (wh

Re: A PicoLisp native library tutorial

2015-03-03 Thread Michel Pelletier
Awesome! On Tue, Mar 3, 2015 at 11:49 AM, Jakob Eriksson wrote: > Yep. > > Definitely interesting. > > > > > On 03/03/15 18:50, Joe Bogner wrote: > > Nicely done. Thanks for sharing > > > > On Tue, Mar 3, 2015 at 12:16 PM, Henrik Sarvell > wrote: > > > >> Nice! > >> > >> On Tue, Mar 3, 2015 at

Re: A PicoLisp native library tutorial

2015-03-03 Thread Rick Hanson
This is great stuff. Nice writing style and very useful for me as a n00b. If Alexander is a n00b, by his own self-profession, then I'm a sub-sub-sub-n00b, because this is good stuff. Thanks! On Tue, Mar 3, 2015 at 11:36 AM, Alexander Williams wrote: > Hi list, > > Some of you might know me from

Re: Solaris 10 picolisp 64 build

2015-03-03 Thread Jakob Eriksson
You are not by any chance on a Sparc platform? On 03/03/15 20:57, Rick Hanson wrote: > Sorry in advance if you’ve already covered this issue in the past. > > I’m on Solaris 10; I can build the 32-bit picolisp (3.1.9) with no problem. > Then, I go do a (cd src64; make) (which is GNU make btw);

Re: Solaris 10 picolisp 64 build

2015-03-03 Thread Rick Hanson
Duh! That's it! And it even says x86 in the name!!! (e.g. `x86-64.sunOs.tgz`) I hereby turn in any computing creds I've garnered over the years to be thrown into burning inferno where they belong, and I'll go live in a box down my the river. :) Thanks! On Tue, Mar 3, 2015 at 4:50 PM, Jakob Erik

Re: Solaris 10 picolisp 64 build

2015-03-03 Thread Rick Hanson
down *by* the river. (I can't even get *that* right.) Cheers! On Tue, Mar 3, 2015 at 5:00 PM, Rick Hanson wrote: > Duh! That's it! And it even says x86 in the name!!! (e.g. > `x86-64.sunOs.tgz`) I hereby turn in any computing creds I've garnered over > the years to be thrown into burning inf

Re: Solaris 10 picolisp 64 build

2015-03-03 Thread Rick Hanson
All, does this mean that picoLisp64 cannot be built on a Solaris 10 sparc64 box? (That's what I have.) If not, no worries; I can, and will be happy to, still use picoLisp32 there. Thanks! On Tue, Mar 3, 2015 at 5:01 PM, Rick Hanson wrote: > down *by* the river. (I can't even get *that* right

Re: A PicoLisp native library tutorial

2015-03-03 Thread Alexander Williams
Thanks Dave. That looks painful, but I look forward to seeing your implementation. On Tue, Mar 3, 2015 at 6:29 PM, Loyall, David wrote: > > From: Alexander Williams > [...] > > I also wrote a tutorial explaining the code, to help other > > newbies understand some useful features of PicoLisp: >

Re: A PicoLisp native library tutorial

2015-03-03 Thread Alexander Williams
Thank you all for your nice comments. On Tue, Mar 3, 2015 at 7:58 PM, Michel Pelletier wrote: > Awesome! > > On Tue, Mar 3, 2015 at 11:49 AM, Jakob Eriksson > wrote: > >> Yep. >> >> Definitely interesting. >> >> >> >> >> On 03/03/15 18:50, Joe Bogner wrote: >> > Nicely done. Thanks for sharing

Re: Solaris 10 picolisp 64 build

2015-03-03 Thread Jakob Eriksson
At this time, that's true. That said, it's not a herculean effort apparently, to port it, given that (correct me Alex or other if I'm wrong) Solaris uses ELF. Uses gas (not sure if it matters) "You" or the person doing the porting knows Sparc assembler. But of course not simple to do either...

Re: Solaris 10 picolisp 64 build

2015-03-03 Thread Alexander Burger
Hi Rick, > All, does this mean that picoLisp64 cannot be built on a Solaris 10 sparc64 > box? Unfortunately yes. I should write the sparc9 support into "src64/arch/", which I have in my to-do list since several years. But it is a lot of work for probably too few use cases. And I still did not ma

Re: Solaris 10 picolisp 64 build

2015-03-03 Thread Alexander Burger
Hi Jakob, > At this time, that's true. That said, it's not a herculean effort > apparently, to port it, given that > (correct me Alex or other if I'm wrong) > Solaris uses ELF. > Uses gas (not sure if it matters) That's true, and this is good. > "You" or the person doing the porting knows Sparc