Subscribe
Hello r...@tamos.net :-) You are now subscribed Just me, rick42, adding an email. (Nothing to see here :) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Windows x64 PicoLisp preview
Hi Joe! Thank you for doing this and nice writeup! I will heed your caveats and use it at work. At first for simple things, and then ramp-up the capabilities related to forking and native calls when they come on-line. This is very exciting, especially for someone like me who is literally stuck using Windoze at the office, but wants to show what picolisp can do for colleagues and clients. The picolisp (language/toolage) fight can be won now. The alternative OS/platform fight will take longer. Hehehe. :) Kind regards, --Rick On Wed, 17 Aug 2016 08:13 -0400, Joe Bogner wrote: > I've been working on a port of PicoLisp 64 to Windows. The port is > ready for an early preview for anyone who wants to try it out > > [...] > > The binaries are available at > https://github.com/joebo/picoLisp-win-x86-64/releases/tag/0.02 > > [...] -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: task db example
On Wed, 24 Aug 2016 09:08 -0400, Joe Bogner wrote: > Some discussion on irc this morning prompted me to create a simple > example showing how to interact with the db directly. > > I posted it to the wiki and am sharing it here in case anyone would > benefit > > http://picolisp.com/wiki/?taskdb Thanks, Joe! I've already seen and tried this a couple of days ago (just "late to the party" on the ML). This is a nice example! -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: toy-forth-in-picolisp, and a 32-bit problem
On Fri, 26 Aug 2016 13:53 +, Jon Kleiser wrote: > Hi, > > This summer I have had some fun trying to figure out how to > implement a super simple toy Forth. For a start, I chose PicoLisp as > an implementation language. You may find it here: > > https://github.com/jkleiser/toy-forth-in-picolisp Very cool! It looks like indeed you had fun. Thanks, Jon! -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: PicoLisp as Femto extension language
On Sun, 04 Sep 2016 19:38 +0200, Thorsten Jolitz wrote: > > Hi List, Hi Thorsten! > recently I found out about Femto, a minimal Emacs implementation in less > than 2k lines of C (including ncurses, though): > > , > | git clone https://github.com/hughbarney/femto.git > ` > > [...] > > There is already a project underway using FemTo-Lisp as extension > language > > , > | git clone https://github.com/FemtoEmacs/Femto-Emacs.git > ` Ah, yes. Very nice! I downloaded this myself and tested it. I can run the flisp code and write my own extensions! (There is a lisp function called `keyboard`[1] that dispatches keychords to lisp functions/functionality.) [1] This function is in `init.lsp` which should be copied from the distro directory into one's home directory. BTW, once I copied it into my home directory, the next time I loaded a C or lisp file into the editor, it was syntax-highlighted. The highlighting has been added via extension language (flisp) code. Nice. > but I thought this would be a perfect use case for an 'AW-style' FFI > library making use of 'native'. Then, PicoLisp could have its own > (Window/Buffer)-Editor, not just the LineEditor, with all the core > Editor-Functions just wrappers around Femto's C-functions. > > But lacking C skills have me stuck in the very beginning: how to turn > this C application into a shared library for 'native', does it even > make sense? > > I guess I should: > > 1. create a shared library for all .c files in the repo except main.c > 2. create the application (main.o) linking the shared library? > > But then, the shared library by itself does not make much sense, it > would need the running C Application to do some useful work (?) Don't see *exactly* what your driving at, but the part you write here, just below, is more clear to me. > So the queston seems rather how to embed PicoLisp in this C Application, > and make Femto extensible in PicoLisp (like Emacs is extensible in Emacs > Lisp) by having FFI wrappers for all core editor functions? Yes, this is more clear to me since that is what Femto-Emacs's author did. Specifically, he yanked out the standard flisp REPL and wired in his own C functions to talk to flisp (i.e. run flisp's eval, capture the result returned and handle the "print" accordingly). flisp itself is compiled and rolled into static libraries and then statically (of course) linked into the Femto-Emacs binary (`femto`). > The > > , > | /home/tj/gitclone/Femto-Emacs/femtolisp > ` > > subdirectory makes the general "Lisp integration task" look rather > complicated, but maybe there is (like so often) a really simple solution > with PicoLisp? Not exactly sure, but I believe that your idea is a doable thing, i.e. that picolisp can just replace femtolisp in the same situation described above. > cheers, > Thorsten Best, --Rick (rick42) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: PicoLisp as Femto extension language
On Sun, 04 Sep 2016 19:38 +0200, Thorsten Jolitz wrote: > The > > , > | /home/tj/gitclone/Femto-Emacs/femtolisp > ` > > subdirectory makes the general "Lisp integration task" look rather > complicated, [...] BTW, this subdirectory `femtolisp` just contains a copy of the original femtolisp repo: https://github.com/JeffBezanson/femtolisp with some of the Femto-Emacs author's tweaks (not much[1]) for embedding femtolisp into Femto-Emacs. ___ [1] The addition of just these files AFAICT: flcall.c and interface2editor.c (which are 770 total LOC), and "ripping out" the REPL in femtolisp, which amounted to deleting 9 lines in `system.lsp` (giving `femtosystem.lsp` and thus `femto.boot`). -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: PicoLisp repository at Bitbucket.org
On Sun, 04 Sep 2016 10:48 +0500, Mansur Mamkin wrote: > Hi all, Hi Mansur! > I've cloned tankfeeder's repository at Bitbucket and installed small > pil-application that checks http://software-lab.de/picoLisp.tgz for > changes and commits to the repo. Repository address is > https://bitbucket.org/mmamkin/picolisp I plan to maintain it while I > have VPS :). Ah, very cool! I like being able to view the diffs for each version (from the one previous to it) in a convenient way and with nice formatting like this. (So, thanks also to tankfeeder whom I understand started this.) Also having a script which checks periodically the "source" and automatically creates a commit for any changes is "icing on the cake". Nice hack! :) > Also we could install there some auto building scripts to provide > fresh deb-package. I would appreciate any ideas and help That sounds cool too. I wish I could help. I don't use Debian (or derivatives). I hope someone is willing to help because it was a shame how Alex asked for an update to the picolisp package in Ubuntu and was getting "crickets". :( Better if we have something like your idea here in play. > Source code is listed below. Comments are welcome I love this script, man. I like the "and chain" in the driver -- reminds me of `A && B && C` in shell. I like how you got it (curl) to check for changes and only if there are, download. And overall it's simple and easy to read. I would want you to be hired on my team because this is the kind of code that I would not mind at all to maintain! Best, --Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Article on fixed-point arithmetic in picolisp
Hello list! Here is a blog post that I wrote about fixed-point number operations in picolisp. http://the-m6.net/blog/fixed-point-arithmetic-in-picolisp.html It was fun to write and I hope you find it useful. It might be a bit tedious for the veterans because it is written to inform a relative newcomer to picolisp about such things. Anyway, as always, I'd appreciate any comment upon it by all you sharp folks who regularly teach me things here and on IRC. Thanks! All the best, --Rick (rick42) P. S. -- I thought that writing this would be fairly easy; then I got into it. :/ When I thought I was finished, I didn't realize that I had more work to do and consequently I delayed publishing for another week. Wow. And that wringer was just *one* post! I don't think I could do an *entire blog* on picolisp as some of you do -- that's for you adventurous and energetic people. :D -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Article on fixed-point arithmetic in picolisp
[Let's try this one more time. I screwed up the headers before. Sorry.] Hello list! Here is a blog post that I wrote about fixed-point number operations in picolisp. http://the-m6.net/blog/fixed-point-arithmetic-in-picolisp.html It was fun to write and I hope you find it useful. It might be a bit tedious for the veterans because it is written to inform a relative newcomer to picolisp about such things. Anyway, as always, I'd appreciate any comment upon it by all you sharp folks who regularly teach me things here and on IRC. Thanks! All the best, --Rick (rick42) P. S. -- I thought that writing this would be fairly easy; then I got into it. :/ When I thought I was finished, I didn't realize that I had more work to do and consequently I delayed publishing for another week. Wow. And that wringer was just *one* post! I don't think I could do an *entire blog* on picolisp as some of you do -- that's for you adventurous and energetic people. :D -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Article on fixed-point arithmetic in picolisp
On 06 Sep 2016, 07:24:00 -0400, Joe Bogner wrote:
> Hey Rick,
Hi Joe!
> Thanks for the article! It was informative and interesting. It
> should make the scale operations less intimidating and awkward to a
> new user. I particularly like how it highlights the benefits over
> floating point math.
Thanks!
> What do you think about publishing some bits from the article on the
> wiki?
Yes, I'd like to post it to the wiki. I would have last night, but I
was running out of time and just became too tired. :)
Also, I think the wiki deserves a shorter, less wordy, version, as I
believe you have suggested ("some bits from the article"), and I
wouldn't mind at all if someone else wanted to take that on.
Otherwise, I will eventually post to the wiki such a version (and of
course, expect others to correct/edit as appropriate).
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: web app example - todo w/mithril.js
Hi Joe! On Wed, 14 Sep 2016 00:14 -0400, Joe Bogner wrote: > I've been working on an example of using PicoLisp to create as a > single page web application (javascript / SPA). > > The code is available at https://github.com/joebo/pil-mithril-todo > > You can play with the example here (may be temporary): > > http://csilo.com:8088/ > > log in with admin/admin > > I welcome any feedback! This is very nice, i.e. a nice digestible, but non-trivial and coherent, example that people can use to learn how to do such as this easily and quickly. It also looks very professional, slick. A question: when you are done typing a task description in the text field, is it possible to have the task added when you then press ENTER there (i.e. without having to press the Add button)? Just wondering. Thanks for doing this! Best, --Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: creating a todo app in less than 2 minutes (pil-mithril-scaffold)
On Thu, 15 Sep 2016 18:13 -0400, Joe Bogner wrote: > I've created a new demo of using PicoLisp with mithril to quickly > prototype apps. > > The key feature is a scaffolding which generates crud operations and > forms for any +ApiEntity > > https://github.com/joebo/pil-mithril-scaffold/blob/master/README.md Coming along nicely! Can't wait for the next version of midipix pil64 to couple with this. -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: FreeBSD 11
On Mon, 10 Oct 2016 21:43 +0300, Mike Pechkin wrote: > Who want or can test for build and test bundled tests on pil32 and 64 on > FreeBSD 11 ? Hi Mike, I won't be able to get around to installing 11 for a bit; so, it's all you, my friend! :) Regarding the announcement btw, it's nice to see that the FreeBSD people accomplished some nice work! Best, --Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: FreeBSD 11
Hi Rowan,
On Tue, 11 Oct 2016 17:47 +0300, Rowan Thorpe wrote:
> On 11 October 2016 at 16:03, Mike Pechkin wrote:
> > I have PIL on every OS it supports, except IRIX.
> > I can update or patch or compile PIL very fast without walls.
>
> I agree for personal use, and it is what I presently do on my
> webhost and personal VMs, but for use at large scale it means
> duplication of effort, risk of inconsistencies from doing manual
> steps,
Answer: don't build with manual steps, use scripts (and test them, of
course).[0] At large scale, orchestration systems do the same thing.
For instance, they sometimes have to install software that is not
pre-built in a canonical package repository.
> barrier to entry for new users,
But picolisp is for experienced programmers[1], a class of people who
have no problem building software.
> less exposure for Picolisp to potential users, etc.
Maybe this is true, but also recall the point about experienced
programmers (who will be the potential users).
> Also, due to the need for auditability and extreme scale with no
> maintenance-overhead my webhost would never agree to manually
> compile/install Picolisp to their public systems from upstream
> source (and definitely not repeatedly for each new release).
But didn't you mention earlier that they allowed you to build picolisp
("it is what I presently do on my webhost")? If so, that's an option.
And you can script your installs and builds for the large(r) scale.
> They would only consider installing a stable package from the "Ports
> tree", hence why I am looking for that.
If they wouldn't let you build picolisp and other software for your
site, you might consider another web hosting service.[2] Seriously.
For all the conveniences and other upsides of ports/packages, they
still have to have maintainers who commit to stay on top of updating
the port. Sometimes that's a lot to ask of someone (who is of course
doing it on a volunteer basis). I've never been a port maintainer
myself, but being on the other side, when ports *don't* get updated,
I've had to nag the maintainer (and nobody likes that) and when that
doesn't get the port updated (not an uncommon case btw), I have to do
the build myself anyway. :(
Of course, this is all just my 2 cents.
Best to you, --Rick
Notes
0. For instance, I myself, on all my platforms -- be they desktop,
laptop, server, it doesn't matter -- use scripts (actually one script
in this case) to install even something as "small" as picolisp:
https://github.com/cryptorick/pilot. Even though the standard
picolisp build is freakin' dead easy, I have other configuration
tweaks that I require to be accomplished pre- and post-build/install,
and I have assurance that "my bases are covered" if I use a script.
So, I'm not telling you to do something that I don't do myself. ;)
1. This is one of the general themes of the Reference,
http://software-lab.de/doc/ref.html.
2. NFSN is (a FreeBSD-based) one that allows the user to build/install
their own software; there are probably others.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: FreeBSD 11
On Fri, 14 Oct 2016 22:12 +0200, Jakob Eriksson wrote: > On 14/10/16 22:01, r...@tamos.net wrote: > > But picolisp is for experienced programmers[1], a class of people who > > have no problem building software. > > Isn't this a bit of a truism. There is nothing in the language > itself making it unsuitable for an UN-experienced programmer. > > Because of various particulars, the barrier is higher to get started in > for a random stranger, but nothing that can't be fixed eventually. I agree, taken out of the original context, as you have it here. But *in context*, the issue is "not having a pre-built package for picolisp will be (among other things) a barrier for new users." I disagree with that. I agree with Mike -- I don't believe it to be necessary. One reason (given in this part) is that the typical new user won't see this as a barrier. They tend not to be rank beginner programmers. (I can't prove this, mind you, but I'm just relying on some anecdotal evidence; so, yes, it's arguable. :) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: is json.l capable to handle escaped quotation marks in strings?
On Sun, 30 Oct 2016 23:23 +0100, O.Hamann wrote:
> (load "@lib/json.l")
> # this works fine:
> (parseJson "{\"sentence\":\"value string with 'single quotes' is valid
> json\"}")
> -> (("sentence" . "value with 'single quotes' is valid json"))
>
> But I don't know how to escape the double quotes (QUOTATION MARK) to
> use instead of the single quotes.
Don't know. Maybe this?
: (parseJson "{\"sentence\":\"value string with \\\"double quotes\\\" is
valid json\"}")
-> (("sentence" . "value string with \"double quotes\" is valid json"))
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Future of PicoLisp?
I never use packages; only build from sources. Just one more data point for you, Alex. ;)
Re: picoLisp in custom Buildroot container now enhanced with vip!
On Sun, 07 May 2017 22:34 -0400, David Bloom wrote: > Various ways to use the container are listed at: > https://hub.docker.com/r/progit/pil-enhanced/ Thanks, and +1 for the Xzibit inspired line in there. :) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Which emacs mode to use?
On Tue, 04 Apr 2017 16:58 -0800, Tim Johnson wrote:
> I'd welcome opinions as to which I should use.
Hi Tim!
Sorry to be "late for the party". I'm not an expert on emacs configs
for picolisp, but I use Thorsten's repo here:
https://github.com/tj64/picolisp-mode.
My `~/.emacs.d/init.el` file has something more involved (to configure
Thorsten's package), but you can get well started with something very
simple like:
```
(add-to-list 'load-path "/path/to/picolisp-mode")
(require 'inferior-picolisp)
(add-to-list 'auto-mode-alist '("\\.l$" . picolisp-mode))
```
where `/path/to/picolisp-mode` is where you cloned the repo into, of
course.
This works because `inferior-picolisp.el` requires `picolisp.el`; so no
need to do the dance the other way. :)
If you already use `use-package` (find it on elpa), it's even a bit
simpler:
```
(add-to-list 'load-path "/path/to/picolisp-mode")
(use-package inferior-picolisp
:mode ("\\.l\\'" . picolisp-mode))
```
The nice thing about `use-package` is that it's a "lazy load" -- it
computes an autoload for you on-the-fly. The actual load will happen
when you open a `.l` file for the first time.
There you go FWIW. Your friend in multiple lisps, --Rick
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Termux-Penti-PicoLisp
Hi Alex! I really like this article. Unfortunately, I couldn't access the vids in Safari on my iPhone. (Yes, an iPhone, but I promise you that I don't wear turtlenecks or berets. :) The video stills look like the triangular "Play" icon with a diagonal slash over it, and I couldn't press anything on or around this to make any video play. I will try on another device tomorrow. Nevertheless, the text is of the high quality of writing to which I am accustomed from you. Best, --Rick
Re: anyone tried cygwin or mingw recently?
On Sun, 02 Jul 2017 19:07 +0200, Richard Z wrote: > Did anyone test it recently? Hi Richard, Hopefully, joebo will comment on this. He is the one I know for sure who has looked into mingw-type builds of picolisp this the past year. Best, --Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: anyone tried cygwin or mingw recently?
Hi, Richard! Curious, if you gave Msys2 a try, as Mike was asking about here: On Thu, 06 Jul 2017 13:07 +0300, Mike Pechkin wrote: > Richard, > > I've compile picoLisp under msys (http://www.msys2.org/) > and 'ctl' locking works here. > You should a try. (Glad to see that joebo chimed in. I wish I could help him too, but I don't think I have the chops or time.) Cheers, --Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Announce: PilBox - Building Android Apps in PicoLisp
On Mon, 18 Sep 2017 14:56 +0200, Alexander Burger wrote: > Hi all, > > finally, an official version of PilBox is out - and a Wiki article: > >https://picolisp.com/wiki/?PilBox Ah! This is wonderful! Thank you! (BTW, in sharing this with a friend today, I characterized this as "a way to dev eschewing icky Java". :) BTW, since I don't have an Android device, I assume that there is a way to VM my way to glory and fame in PilBox dev. :) I have VirtualBox as a base; so, what resources do I additionally need (e.g., iso install) to build a VM? (Sorry, I don't know much about Android, and this is really an Android platform question and not a picolisp/PilBox question, I know.) Thanks for any help. Again, nice work! Yours, --Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Cross Compiling PicoLisp for ARM7
Thanks for the information on this, Mickey! And also thanks for your effort recently tweaking src/Makefile so we could have these useful "hooks". -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Needing a trick with 'de
On Sat, 14 Oct 2017 07:48 +0200, Alexander Burger wrote: > Test: > > [...] > >: (foo (need 3)) >(need 3) >-> 3 Rounding off the test: : (foo (need 3) 'this-and-subsequent-will-be-ignored 42 (/ 1 0)) (need 3) -> 3 Of course. :) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Video of using pil for browsing CSV data
Hi! Thanks for doing this, but I couldn't make it past the first 20 seconds with the flashing lights on the right. They bothered me too much. I appreciate the work that must have been involved which is why I hate to say that I didn't see it (for no other reason than the flashing, of course). Best, --Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: AdventOfCode 2017
On Tue, 02 Jan 2018 17:39 +0200, Mike Pechkin wrote: > p.s. Author of PicoLisp (Alexander Burger) is free for hiring and > CV available by request. Nice touch, tankfeeder. -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: JSON lib rewritten in pure PicoLisp - no C/ffi bindings
Thanks, aw! Your EXPLAINs are something I always look forward to reading, and this one did not disappoint. I also like your style of coding. As an aside, I smiled when you mentioned PAIP. I love this book too! All the best, —Rick
Re: Slides and notes from my Picolisp presentation
“Money” bullet: “Yes, computers can store and handle almost unlimited amounts of code today. But what about you?”
Re: Function similar to Scheme 'foldl'?
On Mon, 08 Oct 2018 19:15 +, Jon Kleiser wrote: > Hi, > > Is there a PicoLisp function similar to the Scheme 'foldl'? Hi Jon! You've probably already gone there, but FWIW this is what I have used in the past. (de foldl (Op Init Xs) (let (Acc Init) (for X Xs (setq Acc (Op Acc X))) Acc)) In action: (de op (X Y) (list 'op X Y)) # The "recon" binary operator :) (test '(op 1 2) (op 1 2)) (test # Normal usage '(op (op (op (op (op 0 1) 2) 3) 4) 5) (foldl op 0 (1 2 3 4 5))) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Function similar to Scheme 'foldl'?
On Tue, 09 Oct 2018 14:24 +, Mike wrote: > My demo code to mimic racket's reference: > https://bitbucket.org/mihailp/tankfeeder/src/default/foldl.l Excellent! I'm stealing this! :) Thanks! -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Function similar to Scheme 'foldl'?
On Tue, 09 Oct 2018 19:31 +0200, Alexander Burger wrote: > On Tue, Oct 09, 2018 at 01:21:07PM -0400, John Duncan wrote: > > Yes, you couldn't reuse the same initial value for a data structure like > > you would in scheme > > How do you mean that? As I said, this code is completely free of destructive > side effects. You can use and reuse any initial value. Indeed. $ pil (de foldl (F I . @) (pass mapc '(@ (setq I (apply F (conc (rest) (cons I ) ) ) -> foldl : (setq I 0) -> 0 : (foldl '+ 0 (1 2 3 4)) -> 10 : I -> 0 "Inside" `foldl` there is some "Hulk smash!"ing going on, but not outside. `foldl` owns `I` and smashes on it with impunity; that's not a problem. -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: FrosCon lighting talk [German]
Thanks for doing this! I wish I knew German so that I could appreciate it (more). Nevertheless, one comment I have -- and it is of course not your fault -- is that they should have provided you with a lapel mic, so that you could type with two hands. (or you could have mastered the penti. :) Solid, man! Again, thanks, freemint! On Fri, 16 Nov 2018 21:23 +0100, Joh-Tob Schäg wrote: > Hi, > > I did an lighting talk on PicoLisp at FrosCon this year. The video is > now out. > My part starts at > https://media.ccc.de/v/froscon2018-2322-lightning_talks#t=975 > While I was terribly exited and my presentation skills where not as good > as they might have been if I prepared more I still wanted to share it. > > Have fun! > freemint > > > > > PÔ” ‘ &j)m¢˜œ¢X¬¦Ê ·«zV›uë.n7œµIì¹» ®&Þ -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Transient Symbol Markup
On Thu, 20 Dec 2018 13:15 +0100, Alexander Burger wrote: > Hi all, > > I will remove the "Transient Symbol Markup" functionality from the > PicoLisp> kernel and some libraries. > > I hope it is OK :) Sounds good to me. I’ve never used tsm-mode in Emacs either (and when I’m pil-ing, I’m in Emacs). Thanks!
Re: 35C3
On Fri, 21 Dec 2018 01:47 +0100, Alexander Shendi (Web.DE) wrote: > Are any picolispers at 35C3? I’m pretty sure beneroth will be there. Have a great time you all!
Re: pgint.l
+1 for writing tests. +1 for using aw-‘s test harness. +1 for having a sane license. Huzzah! :) On Tue, 15 Jan 2019 21:11 +0300, Abel Normand wrote: > Hello everyone, > > I'm happy to announce that I released my small library to > interfacing with> PostgreSQL -- https://gitlab.com/Abel-ze-Normand/pgint.l . I > tried to keep> its implementation as simple as possible. > > I'm open to your suggestions for future improvements and your > contributions. > -- > Best regards, Nail
Re: picolisp-mode
#x27;t have to change anything. Distro package managers are not going to keep up with the latest changes/versions anyway (not in general); so that's another reason I wouldn't count on them to install picolisp. As I told people on irc, I look forward to checking out Alexis's picolisp-mode when I get some time. Looks interesting and useful. This was just my long-winded way of saying what beneroth concisely said: "we don't need one way to rule them all." Just my 2 cents. Cheers, --Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: picolisp-mode
On Tue, 22 Jan 2019 16:11 -05:00, Alexis wrote: > Having said all that, if the PicoLisp community generally felt it > would be best to settle on the mode currently bundled with the > distribution as /the/ Emacs mode for PicoLisp, and wanted me to > remove my mode from MELPA - or at least, rename it - in order to > avoid confusion, i'd be fine with that as well. :-) No! :) First of all, there is no /the/ emacs mode for picolisp. At the very least, that is my personal opinion. beneroth mentioned on irc that there are picolisp users who use each of the known (including yours) picolisp modes. I don't think that they believe there is a "/the/ mode". :) Also, "No!' goes for renaming or removing your code on melpa. Please do not do this. It is unnecessary. I believe that you and the melpa people resolved this correctly. I don't think anybody here believes that you "stole" or "sneaked" your code into melpa before any of the previously written mode authors could (in the "mwahahaha!" style, twirling the end of your mustache :). That would be silly. Anyway, those authors had plenty of time to register their mode with melpa if they wanted to. They didn't. (And you honestly didn't know about the others.) melpa is just not an essential; it's just a nice convenience. I get that milkypostman wants melpa to "win mindshare" or whatever his goals and motives are -- he certainly seems to believe in /the/ way. Hey, as long as I can still source packages from where-ever, the melpa people can do whatever they want. Anyway, that was very admirable of you to consider the community though. Thanks, man! Cheers, --Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: picolisp-mode
Hi Jean-Christophe! On Wed, 23 Jan 2019 02:33 -05:00, Jean-Christophe Helary wrote: > There is also a maintenance issue for the official mode. From what I > understand, there seems to be 3 different versions of that mode and the > authors are not active anymore (and have not been for 6 years)... That's ok. They are working fine for us for years anyway. Many of us (including me) know elisp and can fix them, but honestly, there has never been an issue with them. > In all honesty, if picolisp had not been maintained and updated for 6 > years, would you consider using it ? I don't think you would. I agree. But also,. I would argue that that's not exactly an apples-to-apples comparison. Editor configurations are much easier to work with and much less complex than language and virtual machine implementations. I'll leave the latter to Alex. :) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: picolisp-mode
es in behavior that caused a bit of confusion (no access to
> docs, etc.)
Yes. This is OK, i.e., there are different versions / forks of
picolisp-mode. Pick the one you like.
> There are a number of ways to solve all that in order of
> "completeness" and "complexity":
There seems to be no systemic problem and thus nothing to solve,
except for your personal emacs configuration, if I'm reading your
email correctly.
> I) Document the situation in the picolisp distribution (that won't
> solve the fact that Alexis' mode is not visible in Debian's emacs,
> but at least people will know the issue), that's an easy and
> costless thing to do: edit the wiki and the Readme file. I could do
> that.
I suppose we could mention that there are a few choices of emacs major
modes for picolisp programming and even a rundown of their
functionality / capability. Sounds good. Please do that if you have
time. Thanks.
> II) make Alexis' mode visible in melpa even when running Debian. I'm
> in touch with the Debian packager for picolisp
Alexis's mode is already in melpa. Maybe what you need is the right
setup to get melpa packages listed in the `package-list-packages`
output. This is what I have in my emacs configuration and it works on
whatever OS I'm on.
(setq package-archives
'(("gnu" . "http://elpa.gnu.org/packages/";)
("org" . "http://orgmode.org/elpa/";)
("melpa". "http://melpa.org/packages/";)
("melpa-stable" . "http://stable.melpa.org/packages/";)))
You probably don't need the org one or the melpa-stable one.
(See the other two sources (actually, they're called "archives"; I
called them "services" earlier)? The one labeled "gnu" is the
original ELPA where authors registered packages before mepla came
along. melpa is the bigger archive now by far.)
> If that's only a namespace issue the solution would probably require
> to modify either the picolisp official emacs mode name or Alexis'.
Not needed / necessary.
> a- Considering that the distribution mode is not visible in emacs
> package system, changing its name would be transparent since calling
> the mode is made automatically with emacs hooks. Only when calling
> the mode manually would things differ, in which case the user should
> only remember the new mode name and we're done. Also, it's a one
> time install that is handled by Linux distribution packagers and
> users generally don't have to bother.
Again, not necessary. If you like the picolisp distro's
picolisp-mode, you just copy that into a directory, put that directory
on `load-path` and use the same config bits to load that package.
Here's mine that I use for tj's picolisp-mode, if it helps.
(use-package picolisp
;; Source: https://github.com/tj64/picolisp-mode.git
:load-path "~/.emacs.d/contrib/picolisp-mode"
:mode ("\\.l\\'" . picolisp-mode)
:config
(require 'inferior-picolisp)
(add-hook 'picolisp-mode-hook
(lambda ()
(setq picolisp-program-name "/opt/bin/pil"
I just `git clone`d tj's package under ~/.emacs.d/config and used the
above settings. No melpa or emacs package manager was necessary.
> b- Changing Alexis' mode name requires administrative work on
> Melpa's side, it requires users to manually change the mode, updates
> would not be automatic, etc.
That's another reason why Alexis should *not* rename his package nor
should he remove it from melpa. Alexis and the melpa people got that
right IMO.
> III) make sure that all the goodies that are in the picolisp mode
> are available in Alexis' mode and make Alexis' mode the distribution
> default. That includes inferior-picolisp.el. That requires Alexis to
> work on making sure that there is full compatibility.
Right, that's up to Alexis and anybody willing to help him.
> I checked the paredit patch provided with picolisp, it only adds a
> "paredit-delete-leading-whitespace" function in various places. It
> is probably useful, and why not propose it for inclusion in paredit
> proper ? If it is not accepted, there is probably a way to trigger
> that behavior without having to patch paredit (a hook in the
> picolisp mode ?) but I don't know.
idk either. I don't use paredit.
> IV) Not strictly related, but the picolisp-wiki-mode could be
> transformed into a melpa package. That would be especially useful if
> "picolisp-wiki" (the server-side code) were packaged in Linux
> distributions so as to offer a usable wiki solution at large. That
> would also contribute to increasing picolisp's visibility.
I'm out on that too. I just type in the wiki source with no help from
an editor.
I hope that some of this info helped. Please forgive me if I seemed
in any way lecturing. I just don't really know your skill level with
emacs or admin stuff.
Cheers, --Rick
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: picolisp-mode
Hi Jean-Christophe! Sorry, I forgot to address the other things you mentioned. On Wed, 23 Jan 2019 02:33 -05:00, Jean-Christophe Helary wrote: > The discussion is not about changing anything for people who already > use one or the other mode. It is about proposing something easy to > use *and* not confusing to new comers. OK. I understand. There were also some specific questions or issues that you noticed (e.g., on Debian-like systems) in another email you sent which I took to mean that you did not quite understand how emacs packages can be installed and how emacs can (maybe, should) be configured. I tried to answer that in another email I just sent. Sorry, if I was off base -- was just trying to help. If you already understand all that; then, fantastic. > Besides for the merits of the various modes and the merits of having > multiple modes, I think there is a big documentation issue. It is > easily fixable and since that information is on the wiki that's > something I can fix. That's great. Always strike when the motivation is there, I always say! Glad you are thinking about that. > Then there is literally a ressource visibility issue at least on > Debian. This one is not easy to fix and requires information from > the Debian packager. I can ask for more information and see if there > is a relatively easy fix. The "resource visibility issue" that you described (in your other email) sounded like a misconfigured emacs setup to me. But I'm sure you will look into that to rule out that possibility. Thank you for looking into potential Debian issues. Cheers, --Rick On Wed, 23 Jan 2019 03:01 -05:00, r...@tamos.net wrote: > Hi Jean-Christophe! > > On Wed, 23 Jan 2019 02:33 -05:00, Jean-Christophe Helary wrote: > > There is also a maintenance issue for the official mode. From what I > > understand, there seems to be 3 different versions of that mode and the > > authors are not active anymore (and have not been for 6 years)... > > That's ok. They are working fine for us for years anyway. Many of us > (including me) know elisp and can fix them, but honestly, there has > never been an issue with them. > > > In all honesty, if picolisp had not been maintained and updated for 6 > > years, would you consider using it ? I don't think you would. > > I agree. But also,. I would argue that that's not exactly an > apples-to-apples comparison. Editor configurations are much easier to > work with and much less complex than language and virtual machine > implementations. I'll leave the latter to Alex. :) > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe > -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Hashtable
Hello Kashyap, While not particularly idiomatic, there is some application code here that uses idx, hash and friends which may be of some help, by way of example. Not recommending this for your use, just “yet another example”. :) https://github.com/cryptorick/pil-KVMap/blob/master/KVMap.l Best, Rick
Re: json.l fails to load on pil 64
Indeed. aw is famous for writing stellar doc. This is no exception. https://github.com/aw/picolisp-json/blob/master/EXPLAIN_v3.md#global-variables On Thu, 14 Mar 2019 15:42 -04:00, Abel Normand wrote: > > Hello. > > This error related to namespaces feature in json.l. easy workaround: when run > pil, set env PIL_NAMESPACES=false before pil. This should fix your issue, you > can actually find this solution in official doc for json.l > > Nail. >
Re: SDL2 and OpenGL 3.0+ on Picolisp 64bit (Linux)
>From the project README: > However, in the tests I did, Picolisp performed its fixed-point > arithmetic calculations much faster than I had expected. In the end, > I abandoned the C alternative, but left it there for the records. Excellent! Great to hear. -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: SDL2 and OpenGL 3.0+ on Picolisp 64bit (Linux)
Works on FreeBSD too, if I make this change: $ git diff | cat diff --git a/sdl/findlib.l b/sdl/findlib.l index 20371af..f532cb8 100644 --- a/sdl/findlib.l +++ b/sdl/findlib.l @@ -5,7 +5,7 @@ (de findlib (Lib) (let Matches - (in '(ldconfig "-p") + (in '(ldconfig "-r") (filter '((F) (sub? Lib F)) (make (while (line T) (link @))) ) ) Thanks! (I just found out that I'm terrible at pong :) Best, Rick On Fri, 15 Mar 2019 18:58 -04:00, alfonso.vil...@gmail.com wrote: > Hello, > > I want to share with you my progresses on the following Bitbucket > repository: > > https://bitbucket.org/alfonsovillen/picolispffi/src/master/ > > I would be thankful if someone could take some time to try the demos > and tell me whether they run well. > > Best regards, > Alfonso Villén -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: A good way to write an api server
Thank you, Kashyap! On Sat, 16 Mar 2019 00:34 -04:00, C K Kashyap wrote: > Okay, I have it running finally! > > I have the docker image here - ckkashyap/tools:picolisp-hack- it has IPV4 > based httpgate installed inside :) > The IPV4 version of httpGate is here - > https://github.com/ckkashyap/picoLisp/blob/contrib/src/httpGate.c > > Regards, > Kashayap
Re: PicoLisp for 9-11 years' kids
Hi Christophe! > The project is now stopped because Python must now be used in high > school in France. Too bad. I'm curious now if there was a predecessor to Python as the mandated computer language. If so, what was it? -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: PicoLisp is done
On Mon, 27 May 2019 16:09 -04:00, andr...@itship.ch wrote: > Thread: > https://www.mail-archive.com/picolisp@software-lab.de/msg07057.html Oh yeah. This was from the “the future of PicoLisp is dark” thread. (This was Alex’s quite ominous sounding opening sentence. :)
Re: Portable graphics in PicoLisp
On Mon, 03 Jun 2019 15:44 -04:00, C K Kashyap wrote: > Where do I get the latest version from? > What I have is https://software-lab.de/picoLisp-18.12.tgz >From here: http://software-lab.de/picoLisp.tgz Latest version seems to be 19.6.3. Best, -Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Setup for Emacs org-mode?
Hi Lawrence,
Welcome back to the list!
> Anyone have the definitive setup they could share for picolisp on
> Emacs org-mode?
AFAIK, there is no "definitive setup" in Emacs.
> There seems to be two picolisp-modes
Three is the count I have.
1. picolisp-mode bundled in the picolisp distro.
- N.B. hasn't been updated in years.
2. Thorsten/tj64 version
- https://github.com/tj64/picolisp-mode
- first commit dated Apr 2012
3. Alexis/flexibeast version
- https://github.com/flexibeast/picolisp-mode
- first commit dated Nov 2014
- Lawrence, you might remember discussing #3 with Alexis on this
mailing list back in 2015.
I use #2. However, I had found out about ("got tuned into") #3 back
in January (2019), told Alexis that I'd look at it, but haven't yet.
(Sorry, Alexis.)
So although I happily use #2 without issue, I'd recommend to any one
just picking up a picolisp mode for Emacs to go with #3 (as Alexis is
actively maintaining it).
> and org-mode babel needs the "run-picolisp" inferior mode set, etc.
I use #2 and it works with Org Babel. Thorsten defines `run-picolisp`
in his `inferior-picolisp` here, FYI:
https://github.com/tj64/picolisp-mode/blob/master/inferior-picolisp.el#L357
Not sure about #3, as, as I mentioned, I've yet to use Alexis's
picolisp-mode. If you're up for it, please try it and let us know how
it goes.
My 2 cents (and I hope somebody corrects any errors or omissions on my
part). Happy hacking!
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Yet Another Emacs PicoLisp Mode - hybrid
On Mon, 17 Jun 2019 19:45 -04:00, Grant Shangreaux wrote: > Hello list, Hello, Grant! > I found that I liked features of both tj64 and Alexis' version, so I > decided to make a hybrid of the two. This is little more than > copy-pasting the documentation features from Alexis' version into > the base of the tj64 version. Great choices! I too like the doc facilities in Alexis's version, and I can't live without features from tj64's version like sending expressions to the REPL to be evaluated (e.g. C-x C-e (eval last sexpr)) and full integration with Org Babel. > I don't want to muddy the waters further by creating yet another > picolisp-mode ... No worries. I like the variety. Variation breeds innovation. (Glad, for instance, that Alex was not worried about writing "yet another lisp" -- and we all benefit!) > I would be happy to make a pull-request into the tj64 version if it > is welcome, and Alexis I would be interested in helping to improve > your version as well (especially since it is the one listed on > MELPA). Excellent! I hope they take you up on your offer. Keep up the good work. I may be your next customer, when I get back from my business travel and settle back in. Thanks! Best, Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: why is there no setf in picolisp?
So, reading Alex’s comments and also the definition of the “joke” `setf` here: On Thu, 27 Jun 2019 10:29 -04:00, Mike wrote: > https://github.com/picolisp/picolisp/blob/dev/misc/setf.l informs me that the answer to Bruno’s question is: yes, the concept in fact *does* exist in picolisp (by the use of its `set` primitive), rendering such as a `setf` entirely unnecessary (and un-idiomatic as well).
Re: Limitation of grid from @lib/simul.l
On Mon, 01 Jul 2019 10:49 -04:00, Wojciech Gac wrote: > ... we could have a naming scheme not limited by the 26 columns if > we used lexicographic strings (e.g. a b ... x y z aa ab ... etc). MS Excel! :D -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Limitation of grid from @lib/simul.l
On Mon, 01 Jul 2019 14:50 -04:00, Wojciech Gac wrote: > W dniu poniedziałek, 1 lipca 2019 Mike napisał(a): > > BTW, I have a huge collection of grid usage in my repo: > > https://bitbucket.org/mihailp/tankfeeder/src/default/ > > @Mike, > > Thanks for the link. I'll make sure to have a look. I find the grid > approach appealing, especially after reading "Array Abstinence". For your convenience, here are the files in Mike's collection that appear to use grid. 2048.l 4clojure/hard.l advent2015/code2015.l advent2016/code2016.l advent2017/code2017.l advent2018/code2018.l bfs.l Burger/rosettacode.l exercism-io/a-f.l flood-day14.l flood-fill.l grid-crashme.l grid-warmup.l maze.l Menshikov/2.l Menshikov/3.l rosetta/hidato.l rosetta/numbrix.l rosetta/snusp.l rosetta/ulam.l spiral.l -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: rolling release process
On Sat, 13 Jul 2019 16:03 -04:00, Grant Shangreaux wrote: > On Saturday, July 13, 2019 2:32 PM, Alexander Burger wrote: > > Hi Grant, > > > > > I'd like to switch to the rolling release edition, can you > > > recommend the best way to update? > > > > In such cases I just download https://software-lab.de/picoLisp.tgz > > and then do: > > > > $ tar xfz picoLisp.tgz && cd picoLisp/ && (cd src64; make) > > > > > but what if i have installed other libraries in that directory? > > > > This is no problem, as long as the file names do not conflict. > > Existing files not in the archive will not be touched. > > > > ☺/ A!ex > > That is what i thought should work, I was just unsure. Thanks for > the answer! In addition, I do a "system install" to a tree other than the one used by the system package manager (on most systems, this is /usr/local). So, I usually pick something like /opt or ~/local (for my $PREFIX). And since it can get tedious doing this often (which is implied by "rolling release", right? :), I have script that does it all: from download to build to install. -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: rolling release process
On Sun, 14 Jul 2019 02:07 -04:00, Mike wrote: > my daily use: > # mr up > // if picolisp fetched something new > # cd picolisp/src64 > # make That's really cool, Mike! Thanks! mr is a new one on me. Written by Joey Hess (ikiwiki author). I'm learning about it now: http://myrepos.branchable.com/ Again, thanks! Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: How I run small mailing lists
Nice job, Γιώργο. Thanks!
Re: New PicoLisp CI action on GitHub
On Mon, 18 Nov 2019 02:12 -05:00, AW wrote: > Hi all, > > I've recently published a new "GitHub Action" for PicoLisp, which is > available here: https://github.com/marketplace/actions/picolisp-action WOW! Something more for me to read about too. Thanks, man! -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Picolisp Facebook Page (@picolisp)
Thanks, Taso! (If I were on Facebook I'd join you. :) Best, Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: ORM comparison
On Fri, 29 Nov 2019 01:52 -05:00, Alexander Burger wrote: > Wow beneroth, > > this is a fantastic and overwhelming piece of analyzis! Thanks a lot! > > Perhaps this should be put as an article into the wiki? I second that. beneroth is the man! :) Tour de force! Thanks, mate! -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: freemint in Tokyo
Very cool! Nice shirt BTW, geo. :) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Merry Christmas!!
Χριστός γεννάται! Καλά Χριστούγεννα και ευτυχισμένος ο καινούργιος χρόνος! (Since there are at least 2 Greek pil users on this list and we can also demonstrate more variety in our international flavor!) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: PicoLisp binaries for Linux 32/64 bit
On Wed, 08 Jan 2020 03:44 -05:00, aw wrote: > Hello, > > I've added a [1]GitHub Workflow (https://git.io/Jvezm) which automatically > builds, tests, and packages *every* new version of PicoLisp pushed to the > repo. Cool! Thanks, aw! -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: pil21 repo
On Fri, 21 Feb 2020 03:37 -05:00, Jean-Christophe Helary wrote: > If keeping $20/y is more important than supporting free software, then > I don't see the point spending time (=money) on picolisp, or on free > software in general. I hear you, JC. I’m a member of sr.ht too. Love the concept! Nice to know that there is another “Sir Hatter” here. :) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: PicoLisp on windows
Does anyone realize that there's an LLVM-based port of picolisp being worked on by Alex? :) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Latest pil21 under OpenBSD 6.6-STABLE
On Wed, 15 Apr 2020 00:55 -04:00, Alexander Burger wrote: > Hi Alexander, > > > The latest pil21 (with I/O fns) under OpenBSD/amd64 6.6-STABLE (and most > > probably other BSD-platforms) requires patches to build lib.bc from lib.c. > > It isn't very much, 5 lines or so. > > > > If there is any interest, let me know, I can send the changes tomorrow. I'm > > too tired right now. > > Yes, please. Thanks! I second that. And thank you, both Alexanders! :) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Stop using US controlled software stacks!!!
On Tue, 28 Apr 2020 17:57 -04:00, andr...@itship.ch wrote: > On 28.04.20 22:53, Guido Stepken wrote: > > > > (Blathering removed.) > > You generalize too broadly in one sentence and then contradict > yourself the next. ^^ This. ^^ -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Do free Open Source Foundation's Software Stacks fall under US Export Law?
On Wed, 06 May 2020 17:02 -04:00, Brian Cleary wrote: > It's the end of an error. This was my favorite. hehe. -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Pil21 can bootstrap
Excellent! Thank you and all the best to you in your continued hacking! On Sun, 17 May 2020 07:04 -04:00, Alexander Burger wrote: > Hi all, > > a short note about the Pil21 status: > > It can now bootstrap by itself, meaning that it does no longer need another > PicoLisp to build the *.ll and *.bc files from the sources. > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe > > -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Fridays for Functions (Was: PilCon 2020)
Sounds great! Thanks! -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Fridays for Functions (Was: PilCon 2020)
Sounds great! Thanks! -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: cells in picolisp [tutorial, slides]
On Sat, 06 Jun 2020 06:33 -04:00, Tomas Hlavaty wrote: > nice presentation I agree. Nice job, Mike! -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Auto test your code with Pil21 on GitHub
Thank you, Alex! Thank you, Alex! This is so exciting that I’m thinking about changing my name to Alex to join the club. :D. Seriously, excellent work, guys! On Thu, 27 Aug 2020 22:24 -04:00, Alexander Williams wrote: > Hi all, > > I've updated 'v2' of the "PicoLisp Action" on the GitHub Marketplace. > > It now supports building pil21, and thus allows you to automatically test > your PicoLisp code against the latest pil21, as well as other versions of > pil32 and pil64. > > Have a look here: >https://github.com/marketplace/actions/picolisp-action > > You can see 'All Green' from my initial test runs against 'picolisp-json' > library: >https://github.com/aw/picolisp-json/actions/runs/227965177 > > Although there's still a few things missing in pil21, so far _all_ of my > existing code works with it, so let's encourage and thank Alexander > Burger for his hard work. > > Cheers, > > > AW -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Announcing: Posix Message Queues with PicoLisp
Neat! Yet another cool project. Thank you, AW! On Mon, 09 Nov 2020 23:30 -05:00, Alexander Williams wrote: > Hi, > > I've published some code for interacting with Posix Message Queues[1] > directly in PicoLisp (using 'native'). > >https://github.com/aw/picolisp-posixmq/ > > It's a _very_ small library with quite comprehensive documentation[2] > (WIP). > > And for those who aren't aware, there's also a list of all my PicoLisp > projects available[3]. > > - [1]: https://man7.org/linux/man-pages/man7/mq_overview.7.html > - [2]: https://github.com/aw/picolisp-posixmq/tree/master/docs > - [3]: https://picolisp.a1w.ca/ > > Cheers, > > AW -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re:
“ So technically I don't want to be writing PicoLisp code anymore ...” Yes, I noticed. ;) On Sat, 12 Dec 2020 13:31 -05:00, Erik Gustafson wrote: > Hi list, > > I've published a new article to the wiki: > > https://picolisp.com/wiki/?metaprogrammingexperiments > > It details my continued exploration of writing "Common Lisp style" > macros in PicoLisp > > Enjoy! > > - Erik -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: Pil21 is now in Debian Unstable
Congratulations! \o/ On Tue, 29 Dec 2020 08:23 -05:00, Alexander Burger wrote: > Hi all, > > On Tue, Dec 29, 2020 at 11:29:22AM +, Mike wrote: > > Happy coding and New Year, > > Thanks a lot to Mike Pechkin for all the testing, feedback, input and support, > and to Kan-Ru Chen for maintaining the Debian releases! And to all other > members > in this list and the #picolisp IRC channel! > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe > -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: strong language for blockchain
On Fri, 21 May 2021 13:44 -04:00, andr...@itship.ch wrote: > Regarding blockchain.. well the sole purpose of blockchain is to > operate a distribute database AND operate it by different people who > actively mistrust another. This makes it somewhat suited for crypto > currencies like bitcoin, but there is not really any other meaningful > application. In nearly all real-world scenarios, people can agree on a > single group to be the masters of a database and be trusted. Surely > such a system warrants checks and balances, but still you can then > setup a central database operated by a single actor, [...] > > So in my humble opinion, any real world application of blockchain > technology outside of anti-governmental currency is complete bullshit You're in good company: Bruce Schneier says this too. Blockchain and Trust (February 12, 2019) https://www.schneier.com/blog/archives/2019/02/blockchain_and_.html -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: New Pilog Lisp call syntyx
Nice! Thank you, Alex! On Mon, 26 Jul 2021 05:45 -04:00, Alexander Burger wrote: > Hi all, > > since version 21.7.25 PicoLisp supports a new syntax for calling Lisp code in > Pilog rules. > > As before, the predicate '^' evaluates Lisp expressions inside Pilog code: > >: (? (^ @X (println 'OK))) >OK > @X=OK > > Traditionally, Pilog variables can be accessed with the '->' function: > >: (? @A 3 > (^ @B (inc (-> @A))) ) > @A=3 @B=4 > >: (? @A 3 @B 4 > (^ @N (* (+ (-> @A) (-> @B)) (- (-> @A) (-> @B ) > @A=3 @B=4 @N=-7 > > Now these variables are automatically *bound* before the Lisp code is > evaluated, > so that the following works: > >: (? @A 3 > (^ @B (inc @A)) ) > @A=3 @B=4 > >: (? @A 3 @B 4 > (^ @N (* (+ @A @B) (- @A @B))) ) > @A=3 @B=4 @N=-7 > > The new syntax is shorter and a lot more readable. > > The old syntax continues to work, and '->' is till needed for calls like > >(-> @A 3) > > to access non-top-level Pilog environments. > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe > -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: New blog - "PicoLisp for beginners"
On Wed, 01 Sep 2021 05:57 -04:00, Mia Burger wrote: > > - This is the blog homepage: https://picolisp-blog.hashnode.dev/ > Hi Mia! This is very nice! Thank you! So far, my favorite article is Concepts and Data Types of PicoLisp. Keep up the excellent work! Best, Rick -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: quote form in picolisp
Look for the book to come out soon: “Zen and the Art of Programming Language Development” :) On Thu, 16 Dec 2021 15:48 -05:00, Alexander Burger wrote: > Hi all, > > this whole discussion got ridiculously complicated. > > But in fact it is so simple! > > A function call in PicoLisp is *always* just a single cell: > > +-+--+ > | Fun | Args | > +-+--+ > > Both Fun and Args can be anything (number, symbol or pair). > > If Fun is a number, the expression auto-quotes. Otherwise, while it is a > symbol, > its value is taken. So we end up either with a number (code pointer) or a list > (EXPR, FEXPR, or a mixture of both). This is called with Args. > > Fun is free to do with Args what it wants. > > Who cares about proper or improper lists? Total freedom and power! :) > > 'quote' is the mother of all functions. It does nothing, and just returns > Args. > No need for "special forms"! > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: JavaScript 'lisp' calls
Note:
>From my location the browser does: GET
http://127.0.0.1:8081/!setLocation?39.7670160001&-86.156255
Per Alex:
Since an external (database) symbol starts with dash ('-'), a number
should be prefixed with '+', so a negative number could be specified
with "+-1234567".
Otherwise:
(de setLocation (Lat Lon)
(msg Lat)
(msg Lon) )
returns: 39.76... and NIL; instead of 39.76... & -86.15...
-rl
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: arm
Tomas, Which OS / arm board combination are you using? Thanks, -rl On Sun, Mar 10, 2013 at 7:27 PM, Tomas Hlavaty wrote: > Hi Alex, > > attached is a patch to compile picolisp on arm out of the box. The -m32 > switch doesn't seem to be defined there. > > The -fPIC option was necessary for: > > gcc -o ../lib/z3d -shared -export-dynamic z3d.o > /usr/bin/ld: z3d.o: relocation R_ARM_MOVW_ABS_NC against `a local symbol' > can not be used when making a shared object; recompile with -fPIC > z3d.o: could not read symbols: Bad value > collect2: error: ld returned 1 exit status > make: *** [../lib/z3d] Error 1 > make: Target `picolisp' not remade because of errors. > > Maybe there is a better way to handle the error? > > Would it be possible to include it in the official version? > > Thank you, > > Tomas > > > diff --git a/src/Makefile b/src/Makefile > index 7267011..a229ab8 100644 > --- a/src/Makefile > +++ b/src/Makefile > @@ -7,46 +7,55 @@ lib = ../lib > > picoFiles = main.c gc.c apply.c flow.c sym.c subr.c big.c io.c net.c tab.c > > -CFLAGS = -c -O2 -m32 -pipe \ > +ifeq ($(shell uname -m), armv6l) > + M32 = -fPIC > +else > +ifeq ($(shell uname -m), armv7l) > + M32 = -fPIC > +else > + M32 = -m32 > +endif > +endif > + > +CFLAGS = -c -O2 $(M32) -pipe \ > -falign-functions -fomit-frame-pointer -fno-strict-aliasing \ > -W -Wimplicit -Wreturn-type -Wunused -Wformat \ > -Wuninitialized -Wstrict-prototypes \ > -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 > > - > ifeq ($(shell uname), Linux) > OS = Linux > - PICOLISP-FLAGS = -m32 -rdynamic > + PICOLISP-FLAGS = $(M32) -rdynamic > LIB-FLAGS = -lc -lm -ldl > - DYNAMIC-LIB-FLAGS = -m32 -shared -export-dynamic > + DYNAMIC-LIB-FLAGS = $(M32) -shared -export-dynamic > STRIP = strip > else > ifeq ($(shell uname), OpenBSD) > OS = OpenBSD > - PICOLISP-FLAGS = -m32 -rdynamic -Wl,-E > + PICOLISP-FLAGS = $(M32) -rdynamic -Wl,-E > LIB-FLAGS = -lc -lm > DYNAMIC-LIB-FLAGS = -Wl,-E -Wl,-shared > STRIP = strip > else > ifeq ($(shell uname), FreeBSD) > OS = FreeBSD > - PICOLISP-FLAGS = -m32 -rdynamic > + PICOLISP-FLAGS = $(M32) -rdynamic > LIB-FLAGS = -lc -lm > - DYNAMIC-LIB-FLAGS = -m32 -shared -export-dynamic > + DYNAMIC-LIB-FLAGS = $(M32) -shared -export-dynamic > STRIP = strip > else > ifeq ($(shell uname), NetBSD) > OS = NetBSD > - PICOLISP-FLAGS = -m32 -rdynamic > + PICOLISP-FLAGS = $(M32) -rdynamic > LIB-FLAGS = -lc -lm > - DYNAMIC-LIB-FLAGS = -m32 -shared -export-dynamic > + DYNAMIC-LIB-FLAGS = $(M32) -shared -export-dynamic > STRIP = strip > else > ifeq ($(shell uname), Darwin) > OS = Darwin > - PICOLISP-FLAGS = -m32 > + PICOLISP-FLAGS = $(M32) > LIB-FLAGS = -lc -lm -ldl > - DYNAMIC-LIB-FLAGS = -m32 -dynamiclib -undefined dynamic_lookup > + DYNAMIC-LIB-FLAGS = $(M32) -dynamiclib -undefined dynamic_lookup > STRIP = strip -x > else > ifeq ($(shell uname -o), Cygwin) > >
Re: arm
re: Rpi: re: Debian Linux: as downloaded from raspberrypi.org. gcc reported -m32 as an invalid option. I removed it. after building picoLisp: /pil ./app/main.l -main -go + !? (port 4040) IP socket error: Address family not supported by protocol ? The default Debian download is ipv4. per Alex: "If you absolutely have to use IPv4, you might download an older version, e.g. http://software-lab.de/picoLisp-3.0.8.tgz, but this is rather unsatisfactory." There may be a newer version of Debian w/ ipv6 support. When last I checked I found some "independent" builds; however it looked like the were as likely to crash, as not. (re: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=5069) re: Rpi: re: Arch Linux: Arch on Rpi supports ipv6 and worked (I think after removing -m32, as above, in the make file. I will have to look for my notes.) Question: Has anyone tried PicoLisp on a Google Nexus device w/ Ubuntu Touch? -rl On Thu, Mar 21, 2013 at 5:16 PM, Tomas Hlavaty wrote: > Hi Rick, > > > Which OS / arm board combination are you using? > > linux, pandaboard, beagleboard, rpi. > > Cheers, > > Tomas > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
Re: arm
Tomas, I did not have an -fPIC issue. Maybe because I removed -m32? Thanks, -rl On Fri, Mar 22, 2013 at 4:49 AM, Tomas Hlavaty wrote: > Hi Rick, > > > re: Rpi: > > re: Arch Linux: > > > > Arch on Rpi supports ipv6 and worked (I think after removing -m32, as > > above, in the make file. I will have to look for my notes.) > > and the -fPIC issue? > > Thanks, > > Tomas > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
Re: arm
Tomas, I will look up my notes; and, try a re-compile tomorrow: will let you know... -rl On Fri, Mar 22, 2013 at 8:08 AM, Rick Lyman wrote: > Tomas, > > I did not have an -fPIC issue. Maybe because I removed -m32? > > Thanks, > > -rl > > > On Fri, Mar 22, 2013 at 4:49 AM, Tomas Hlavaty wrote: > >> Hi Rick, >> >> > re: Rpi: >> > re: Arch Linux: >> > >> > Arch on Rpi supports ipv6 and worked (I think after removing -m32, as >> > above, in the make file. I will have to look for my notes.) >> >> and the -fPIC issue? >> >> Thanks, >> >> Tomas >> -- >> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >> > >
Subscribe
Add me, baby! ;-)
Re: PicoLisp GUI on Smartphones
re: HTML5 What future features are being worked on? Thanks Alex, -rl On Mon, Dec 23, 2013 at 10:18 AM, Alexander Burger wrote: > Hi all, > > it is quite straightforward to use the standard PicoLisp GUI on > smartphones, basically by including a CSS file and new menu > function. More about this on > >http://picolisp.com/5000/!wiki?PhoneGUI > > The article presents a simple demo, and describes how to access it. > > A merry Christmas and a Happy New Year to everyone! > > ♪♫ Alex > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
Re: websocketd, tested with pil32 and ersatz/pil
Jon, Have you tried this: https://bitbucket.org/cyborgar/web.l/src/249fe9f5c7d8/web/sockets.l -rl On Tue, Dec 31, 2013 at 10:02 AM, Alexander Burger wrote: > Hi Jon, > > > server, and I have discovered that PicoLisp (at least the 32-bit), > > behaves a little different from other "applications" (incl. bash and > > ersatz/pil). > > ... > > websocketd --port=8080 -devconsole pil > > (You get cleaner results back from PicoLisp if you don't add the "+" > > after "pil".) > > ... > > ersatz/pil and other "applications", is that if you click the > > disconnect button, then pil32 is not terminated. On my Mac it > > instead starts using close to 100% CPU, and I have to kill it > > manually. If I, instead of clicking disconnect, type "(bye)", then > > PicoLisp terminates and I get a 'disconnect'. > > I haven't tried exactly this example, but I think I can explain the > behavior. > > The runtime behavior of PicoLisp differs from other applications in that > it evaluates all command-line arguments, and then goes into an infinite > loop (REPL). This means specifically that (bye) must be called > eventually. In debug mode, the REPL line editor takes care of that, by > calling (bye) when Ctrl-D is hit. > > Perhaps it is a bug that EOF on STDIN is not handled more gracefully, > and I'm not sure at the moment what it would involve. > > "Barebone" stdio-programs like bash, ersatzLisp, but also e.g. > miniPicoLisp terminate despite of that, because they don't set up a > special handler for the console. > > In any case, scripts like yours > > > #!/usr/bin/picolisp /usr/lib/picolisp/lib.l > > (load "@lib/misc.l") > > > > (in NIL > >(use (Exe Res) > > (until (eof) > > (setq Exe (read)) > > (prin "-> ") > > (println > > (setq Res > > (let @ Res > >(eval Exe) ) ) ) > > (flush) ) ) ) > > should always call (bye) in the end (i.e. after 'until' or the enclosing > 'in' terminated). > > > > > Something else is that output that goes to STDERR, does not show up > > in the browser (it ends up in the websocketd log), and I guess that > > is why I don't see any response if I type something like "(foo)", > > where 'foo' is undefined. Can output to STDERR in an easy way be > > redirected to STDOUT in a REPL script? > > Yes, this should be doable with (err NIL ...) > > ♪♫ Alex > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
Re: PicoLisp GUI on Smartphones
Alex, I trust that you had a merry Christmas and a Happy New Year... Supporting phones is a very good idea: " http://www.digitaltrends.com/mobile/mobile-phone-world-population-2014/"; The article mentions: "Of the 6 billion cell phones in use, only around 1.1 billion of them are mobile-broadband devices." I wonder what market size Mozilla is expecting for Firefox OS. Prior to you mentioning: "http://www.w3.org/2009/dap/";; I had not thought of the browser supporting some of the same features as Firefox OS. I have mixed feelings about: "this would break the fundamental rule that the GUI should also work in an environment without JavaScript" It seems contrary to what most companies are pursuing, e.g.: " http://www.sencha.com/blog/the-making-of-fastbook-an-html5-love-story"; Anyway, have you looked at: "https://github.com/kripken/emscripten/wiki"; and "http://asmjs.org/faq.html";? I suppose that PicoLisp could run in the browser; and, act as an offline cache for the server, etc Some of the same code could also be used in nodeJS; for OS interop, etc... Under Windows I have used nodeJS so that localhost can query PicoLisp, in a psuedo RESTful manner (i.e., no app session...) Thanks, -rl On Wed, Dec 25, 2013 at 7:35 AM, Alexander Burger wrote: > Hi Jon, > > thanks for the input! > > > Numerical input elements can/should be given pattern attributes that > > trigger the numerical keypad on iPhones/iPads, like this: > > > > As far as I know, this pattern makes no difference on Android. ;-) > > This could be easily done using the '
Re: PicoLisp GUI on Smartphones
Thanks Henrik and Alex,
This came in my email this morning: "
http://us5.campaign-archive1.com/?u=502910cc28cb186a9e829f748&id=a8605b778a&e=9d2ada32e2
"
It seems to me that the easiest way to overcome server volume(1)
limitations ("http://www.kegel.com/c10k.html";), is by executing a much as
possible on the client. See also: "http://www.generalinterface.org/";.
(Disclosure: my at work architecture is Oracle/Microsoft SQL Server and
net. Sometimes General Interface is the UI.)
I will create, and share, some (HTML5 and/or General Interface and/or
TiddlyWiki)+PicoLisp examples; hopefully soon.(2)
Alex, thanks for pointing me to: "http://getfri.es/"; and "
https://github.com/jaunesarmiento/fries";. Do you use this for testing; or,
for production?
Thanks,
-rl
(1) Not that I have this problem (no volume, ha ha).
(2) A non PicoLisp experiment: http://ricklyman.net/gi4.html
On Mon, Jan 6, 2014 at 2:19 AM, Alexander Burger wrote:
> Hi Rick,
>
> a Happy New Year to you too! And to everybody else, of course! :)
>
>
> And thanks for the feedback and links.
>
> > I have mixed feelings about: "this would break the fundamental rule that
> > the GUI should also work in an environment without JavaScript"
> >
> > It seems contrary to what most companies are pursuing, e.g.: "
> > http://www.sencha.com/blog/the-making-of-fastbook-an-html5-love-story";
>
> Sure, that's true. And in fact we are currently also using Phonegap and
> fries.js in the same project.
>
> Still it is an important feature for me if an application works _also_
> without JavaScript and cookies, running in plain text browsers or
> scrape-script-driven, without any limits to handicapped persons (screen
> readers) or in otherwise restricted environments. Another gain is
> performance because of the lightweight.
>
>
> > Under Windows I have used nodeJS so that localhost can query PicoLisp,
> in a
> > psuedo RESTful manner (i.e., no app session...)
>
> Yes, and you can use PicoLisp in that way also in the standard setup. I
> do this for simple static pages.
>
> But I strongly disagree in non-trivial cases. The session-oriented
> protocol of a PicoLisp app is a must for me. A stateless paradigm like
> REST (keeping the state in the client instead of the server) would IMHO
> be by far inferior for the kind of applications I'm dealing with. As a
> matter of principle some state must be hold in the database on the
> server, and therefore also most decisions concerning the flow, so
> delegating some part of the state to the client gives a very unmodular
> program structure.
>
> ♪♫ Alex
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>
Re: PicoLisp GUI on Smartphones
http://www.engadget.com/2014/01/06/firefox-os-tablet-developer-program/
http://www.engadget.com/2014/01/06/panasonic-firefox-os-deal/
On Mon, Jan 6, 2014 at 10:15 AM, Rick Lyman wrote:
> Thanks Henrik and Alex,
>
> This came in my email this morning: "
> http://us5.campaign-archive1.com/?u=502910cc28cb186a9e829f748&id=a8605b778a&e=9d2ada32e2
> "
>
> It seems to me that the easiest way to overcome server volume(1)
> limitations ("http://www.kegel.com/c10k.html";), is by executing a much as
> possible on the client. See also: "http://www.generalinterface.org/";.
> (Disclosure: my at work architecture is Oracle/Microsoft SQL Server and
> .net. Sometimes General Interface is the UI.)
>
> I will create, and share, some (HTML5 and/or General Interface and/or
> TiddlyWiki)+PicoLisp examples; hopefully soon.(2)
>
> Alex, thanks for pointing me to: "http://getfri.es/"; and "
> https://github.com/jaunesarmiento/fries";. Do you use this for testing;
> or, for production?
>
> Thanks,
>
> -rl
>
> (1) Not that I have this problem (no volume, ha ha).
> (2) A non PicoLisp experiment: http://ricklyman.net/gi4.html
>
>
>
> On Mon, Jan 6, 2014 at 2:19 AM, Alexander Burger wrote:
>
>> Hi Rick,
>>
>> a Happy New Year to you too! And to everybody else, of course! :)
>>
>>
>> And thanks for the feedback and links.
>>
>> > I have mixed feelings about: "this would break the fundamental rule that
>> > the GUI should also work in an environment without JavaScript"
>> >
>> > It seems contrary to what most companies are pursuing, e.g.: "
>> > http://www.sencha.com/blog/the-making-of-fastbook-an-html5-love-story";
>>
>> Sure, that's true. And in fact we are currently also using Phonegap and
>> fries.js in the same project.
>>
>> Still it is an important feature for me if an application works _also_
>> without JavaScript and cookies, running in plain text browsers or
>> scrape-script-driven, without any limits to handicapped persons (screen
>> readers) or in otherwise restricted environments. Another gain is
>> performance because of the lightweight.
>>
>>
>> > Under Windows I have used nodeJS so that localhost can query PicoLisp,
>> in a
>> > psuedo RESTful manner (i.e., no app session...)
>>
>> Yes, and you can use PicoLisp in that way also in the standard setup. I
>> do this for simple static pages.
>>
>> But I strongly disagree in non-trivial cases. The session-oriented
>> protocol of a PicoLisp app is a must for me. A stateless paradigm like
>> REST (keeping the state in the client instead of the server) would IMHO
>> be by far inferior for the kind of applications I'm dealing with. As a
>> matter of principle some state must be hold in the database on the
>> server, and therefore also most decisions concerning the flow, so
>> delegating some part of the state to the client gives a very unmodular
>> program structure.
>>
>> ♪♫ Alex
>> --
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>
>
>
Re: PicoLisp GUI on Smartphones
Alex,
> and the load distributed across multiple servers.
How so? Currently PicoLisp forks on the same sever. Are you using remote
queries to other PicoLisp instances? A proxy to parse routes?
re: "https://www.mail-archive.com/picolisp@software-lab.de/msg00097.html";
> For production. At the moment the project is still in prototype stage.
How does fries.js GET and POST to PicoLisp? JSON converted to PicoLisp
objects?
re: "http://www.prodevtips.com/2008/09/11/pico-lisp-and-json/"; (:Thanks
Henrik)
Thanks,
-rl
On Tue, Jan 7, 2014 at 1:52 AM, Alexander Burger wrote:
> Hi Rick,
>
> > It seems to me that the easiest way to overcome server volume(1)
> > limitations ("http://www.kegel.com/c10k.html";), is by executing a much
> as
> > possible on the client. See also: "http://www.generalinterface.org/";.
>
> It all depends on the application. But, in my experience, the relative
> load on the server is quite low in the current PicoLisp architecture.
>
> Some things _have_ to be done on the server anyway, like validations and
> synchronizations, so you can't put much on the client alone.
>
> Also, the client does the most work anyway. The bottleneck is rendering
> the layout in the browser, not the virtual representation of the GUI
> components on the server. You can see that easily with 'top', if you run
> both the client and server on a single machine.
>
> And with tens of thousands of clients (doing heavy database work, not
> just static pages) the situation needs to be analyzed carefully, and the
> load distributed across multiple servers.
>
>
> > Alex, thanks for pointing me to: "http://getfri.es/"; and "
> > https://github.com/jaunesarmiento/fries";. Do you use this for testing;
> or,
> > for production?
>
> For production. At the moment the project is still in prototype stage.
>
> ♪♫ Alex
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>
Re: Altering web app framework look via a css framework
Not PicoLisp; but you may want to look at: http://foundation.zurb.com/docs/css.html. On Sun, Feb 16, 2014 at 1:51 PM, me wrote: > Hello List, > > Are there any pro tips for how could I go about adding/altering css > styling via a css framework like bootstrap for example? Including the > necessary files is no problem but I'm finding it difficult to specify CSS > classes and such for gui components. Thank you in advance for your help. >
Re: JSON Rest
Look at this post: http://blog.gmane.org/gmane.lisp.picolisp.general/month=20121001. For session management you may want to look at: http://picolisp.com/wiki/?macropis. On Mon, Feb 17, 2014 at 1:44 PM, klaus schilling wrote: > hello, > is it possible to write a client for a JSON rest service in picolisp? > > Many services abandon their XML-RPC API and flee to JSON rets, for > whatever reason. > > Klaus Schilling > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
Re: Regarding the implementations of PicoLisp
Christophe, How about porting the c version using: https://github.com/kripken/emscripten ? -rl On Thu, May 8, 2014 at 5:08 PM, Christophe Gragnic < christophegrag...@gmail.com> wrote: > Hi, > > I'm currently embedding a «pedagogical pseudo-code like language» in > PicoLisp. > As using plain browsers is a nice thing to have in front of students, > I tried with > EmuLisp (PicoLisp in JS, by Jon Kleiser, that I won't thank enough, with > Alex), > which proved to be a good solution for me. > > So I had some thoughts, ideas and questions. > > 1) EmuLisp lacks some functions. The first idea I had was to write them in > the > available functions (like 'glue' with 'pack'). It worked for some, but > some others > needed to be implemented in JS. Now my question: how far could be pushed > the > idea to write a maximal subset of Picolisp in a minimal subset of > Picolisp? Like in > the original paper of McCarthy or «the Jewel» in SICP? I'm not talking > about > performance here, just functions availability. > > 2) Since PicoLisp64 is written in a «generic assembly» embedded in > PicoLisp, > I was wondering (only wondering, since the concepts are a bit vague for > me) if > instead of building the .s files we could build some http://asmjs.org/file(s). > > 3) Regarding EmuLisp again, and for your information, I've created > (and am using seriously!) a JS pil, that I named `piljs` which runs on node
Re: Regarding the implementations of PicoLisp
Joe, Something like: Browser Stream IN miniPicoLisp (c to asm.js via emscripten) PiL i/o read-eval-print loop Stream OUT HTML, PiL i/o to Server, JSON, ... localStorage, indexedDB, cookies, sessionStorage, ... Server Stream IN PicoLisp PiL i/o from miniPicoLisp/Browser read-eval-print loop Stream OUT PiL i/o to Browser/miniPicoLisp http://software-lab.de/doc/ref.html#io: ...read-eval-print loop... http://software-lab.de/doc/tut.html#funio: ...functions operate on implicit input and output channels... http://picolisp.com/wiki/?ideasPage: ...pilBrowserDB... -rl On Fri, May 9, 2014 at 8:19 AM, Joe Bogner wrote: > Hi Rick, Christophe, > > I was thinking the same thing. miniPicolisp might be a simpler first step > to port > > > On Fri, May 9, 2014 at 7:51 AM, Rick Lyman > > > wrote: > >> Christophe, >> >> How about porting the c version using: >> https://github.com/kripken/emscripten? >> >> -rl >> >> >> On Thu, May 8, 2014 at 5:08 PM, Christophe Gragnic < >> christophegrag...@gmail.com> wrote: >> >>> Hi, >>> >>> I'm currently embedding a «pedagogical pseudo-code like language» in >>> PicoLisp. >>> As using plain browsers is a nice thing to have in front of students, >>> I tried with >>> EmuLisp (PicoLisp in JS, by Jon Kleiser, that I won't thank enough, with >>> Alex), >>> which proved to be a good solution for me. >>> >>> So I had some thoughts, ideas and questions. >>> >>> 1) EmuLisp lacks some functions. The first idea I had was to write them >>> in the >>> available functions (like 'glue' with 'pack'). It worked for some, but >>> some others >>> needed to be implemented in JS. Now my question: how far could be pushed >>> the >>> idea to write a maximal subset of Picolisp in a minimal subset of >>> Picolisp? Like in >>> the original paper of McCarthy or «the Jewel» in SICP? I'm not talking >>> about >>> performance here, just functions availability. >>> >>> 2) Since PicoLisp64 is written in a «generic assembly» embedded in >>> PicoLisp, >>> I was wondering (only wondering, since the concepts are a bit vague for >>> me) if >>> instead of building the .s files we could build some >>> http://asmjs.org/file(s). >>> >>> 3) Regarding EmuLisp again, and for your information, I've created >>> (and am using seriously!) a JS pil, that I named `piljs` which runs on >>> node >> >> >> >
Re: Regarding the implementations of PicoLisp
Joe, Christophe,
re: miniPicoLisp (c to asm.js via emscripten) and stream management:
Simlarly maybe "Query" could be adapted via emscripten:
https://github.com/tj64/picolisp-by-example/blob/master/mainmatter/rosettacode-C.tex
"[
Calling a PicoLisp function from another program requires a running
interpreter.
There are several possibilities, like IPC via fifo's or sockets using the
PLIO
(PicoLisp-I/O) protocol, but the easiest is calling the interpreter in a
pipe.
This is relatively efficient, as the interpreter's startup time is quite
short.
]"
"[
int Query(char *Data, size_t *Length) {
FILE *fp;
char buf[64];
sprintf(buf, "/usr/bin/picolisp query.l \%d -bye", *Length);
if (!(fp = popen(buf, "r")))
return 0;
fgets(Data, *Length, fp);
*Length = strlen(Data);
return pclose(fp) >= 0 \&\& *Length != 0;
}
]"
On Fri, May 9, 2014 at 8:19 AM, Joe Bogner wrote:
> Hi Rick, Christophe,
>
> I was thinking the same thing. miniPicolisp might be a simpler first step
> to port
>
>
> On Fri, May 9, 2014 at 7:51 AM, Rick Lyman
>
> > wrote:
>
>> Christophe,
>>
>> How about porting the c version using:
>> https://github.com/kripken/emscripten?
>>
>> -rl
>>
>>
>> On Thu, May 8, 2014 at 5:08 PM, Christophe Gragnic <
>> christophegrag...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I'm currently embedding a «pedagogical pseudo-code like language» in
>>> PicoLisp.
>>> As using plain browsers is a nice thing to have in front of students,
>>> I tried with
>>> EmuLisp (PicoLisp in JS, by Jon Kleiser, that I won't thank enough, with
>>> Alex),
>>> which proved to be a good solution for me.
>>>
>>> So I had some thoughts, ideas and questions.
>>>
>>> 1) EmuLisp lacks some functions. The first idea I had was to write them
>>> in the
>>> available functions (like 'glue' with 'pack'). It worked for some, but
>>> some others
>>> needed to be implemented in JS. Now my question: how far could be pushed
>>> the
>>> idea to write a maximal subset of Picolisp in a minimal subset of
>>> Picolisp? Like in
>>> the original paper of McCarthy or «the Jewel» in SICP? I'm not talking
>>> about
>>> performance here, just functions availability.
>>>
>>> 2) Since PicoLisp64 is written in a «generic assembly» embedded in
>>> PicoLisp,
>>> I was wondering (only wondering, since the concepts are a bit vague for
>>> me) if
>>> instead of building the .s files we could build some
>>> http://asmjs.org/file(s).
>>>
>>> 3) Regarding EmuLisp again, and for your information, I've created
>>> (and am using seriously!) a JS pil, that I named `piljs` which runs on
>>> node
>>
>>
>>
>
Re: Regarding the implementations of PicoLisp
Joe, Christophe, A downside to asm.js is that it is Firefox only... http://www.infoworld.com/t/javascript/apple-has-its-own-javascript-accelerator-in-the-works-242042 -rl p.s.: anyone considering c directly via Chrome/NaCL? On Fri, May 9, 2014 at 8:19 AM, Joe Bogner wrote: > Hi Rick, Christophe, > > I was thinking the same thing. miniPicolisp might be a simpler first step > to port > > > On Fri, May 9, 2014 at 7:51 AM, Rick Lyman > > > wrote: > >> Christophe, >> >> How about porting the c version using: >> https://github.com/kripken/emscripten? >> >> -rl >> >> >> On Thu, May 8, 2014 at 5:08 PM, Christophe Gragnic < >> christophegrag...@gmail.com> wrote: >> >>> Hi, >>> >>> I'm currently embedding a «pedagogical pseudo-code like language» in >>> PicoLisp. >>> As using plain browsers is a nice thing to have in front of students, >>> I tried with >>> EmuLisp (PicoLisp in JS, by Jon Kleiser, that I won't thank enough, with >>> Alex), >>> which proved to be a good solution for me. >>> >>> So I had some thoughts, ideas and questions. >>> >>> 1) EmuLisp lacks some functions. The first idea I had was to write them >>> in the >>> available functions (like 'glue' with 'pack'). It worked for some, but >>> some others >>> needed to be implemented in JS. Now my question: how far could be pushed >>> the >>> idea to write a maximal subset of Picolisp in a minimal subset of >>> Picolisp? Like in >>> the original paper of McCarthy or «the Jewel» in SICP? I'm not talking >>> about >>> performance here, just functions availability. >>> >>> 2) Since PicoLisp64 is written in a «generic assembly» embedded in >>> PicoLisp, >>> I was wondering (only wondering, since the concepts are a bit vague for >>> me) if >>> instead of building the .s files we could build some >>> http://asmjs.org/file(s). >>> >>> 3) Regarding EmuLisp again, and for your information, I've created >>> (and am using seriously!) a JS pil, that I named `piljs` which runs on >>> node >> >> >> >
Re: Regarding the implementations of PicoLisp
Joe, Christophe, Some links: http://ricklyman.net:81/!wiki?emscripten On Thu, May 8, 2014 at 5:08 PM, Christophe Gragnic < christophegrag...@gmail.com> wrote: > Hi, > > I'm currently embedding a «pedagogical pseudo-code like language» in > PicoLisp. > As using plain browsers is a nice thing to have in front of students, > I tried with > EmuLisp (PicoLisp in JS, by Jon Kleiser, that I won't thank enough, with > Alex), > which proved to be a good solution for me. > > So I had some thoughts, ideas and questions. > > 1) EmuLisp lacks some functions. The first idea I had was to write them in > the > available functions (like 'glue' with 'pack'). It worked for some, but > some others > needed to be implemented in JS. Now my question: how far could be pushed > the > idea to write a maximal subset of Picolisp in a minimal subset of > Picolisp? Like in > the original paper of McCarthy or «the Jewel» in SICP? I'm not talking > about > performance here, just functions availability. > > 2) Since PicoLisp64 is written in a «generic assembly» embedded in > PicoLisp, > I was wondering (only wondering, since the concepts are a bit vague for > me) if > instead of building the .s files we could build some http://asmjs.org/file(s). > > 3) Regarding EmuLisp again, and for your information, I've created > (and am using seriously!) a JS pil, that I named `piljs` which runs on node
Re: Regarding the implementations of PicoLisp
re: http://pypyjs.org/demo/ Success: Chrome: 34 Internet Explorer: 11 Failure: Safari: 5 On Fri, May 9, 2014 at 10:50 AM, Joe Bogner wrote: > It works in chrome too and IE10 too > > Check out: http://pypyjs.org/demo/ > > > > > On Fri, May 9, 2014 at 10:21 AM, Rick Lyman wrote: > >> Joe, Christophe, >> >> A downside to asm.js is that it is Firefox only... >> >> >> http://www.infoworld.com/t/javascript/apple-has-its-own-javascript-accelerator-in-the-works-242042 >> >> -rl >> >> p.s.: anyone considering c directly via Chrome/NaCL? >> >> >> On Fri, May 9, 2014 at 8:19 AM, Joe Bogner wrote: >> >>> Hi Rick, Christophe, >>> >>> I was thinking the same thing. miniPicolisp might be a simpler first >>> step to port >>> >>> >>> On Fri, May 9, 2014 at 7:51 AM, Rick Lyman >>> >>> > wrote: >>> >>>> Christophe, >>>> >>>> How about porting the c version using: >>>> https://github.com/kripken/emscripten? >>>> >>>> -rl >>>> >>>> >>>> On Thu, May 8, 2014 at 5:08 PM, Christophe Gragnic < >>>> christophegrag...@gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> I'm currently embedding a «pedagogical pseudo-code like language» in >>>>> PicoLisp. >>>>> As using plain browsers is a nice thing to have in front of students, >>>>> I tried with >>>>> EmuLisp (PicoLisp in JS, by Jon Kleiser, that I won't thank enough, >>>>> with Alex), >>>>> which proved to be a good solution for me. >>>>> >>>>> So I had some thoughts, ideas and questions. >>>>> >>>>> 1) EmuLisp lacks some functions. The first idea I had was to write >>>>> them in the >>>>> available functions (like 'glue' with 'pack'). It worked for some, but >>>>> some others >>>>> needed to be implemented in JS. Now my question: how far could be >>>>> pushed the >>>>> idea to write a maximal subset of Picolisp in a minimal subset of >>>>> Picolisp? Like in >>>>> the original paper of McCarthy or «the Jewel» in SICP? I'm not talking >>>>> about >>>>> performance here, just functions availability. >>>>> >>>>> 2) Since PicoLisp64 is written in a «generic assembly» embedded in >>>>> PicoLisp, >>>>> I was wondering (only wondering, since the concepts are a bit vague >>>>> for me) if >>>>> instead of building the .s files we could build some >>>>> http://asmjs.org/file(s). >>>>> >>>>> 3) Regarding EmuLisp again, and for your information, I've created >>>>> (and am using seriously!) a JS pil, that I named `piljs` which runs on >>>>> node >>>> >>>> >>>> >>> >> >
