newlispfanclub.alh.net

Excellent, Lutz. Kudos for the quick announcement.

Hi, Mark, The dolist iterates the list one element at a time. Because you're not printing in that loop, the interpreter is silently throwing away each internal result. Finally the result of the whole loop (its final evaluation) is shown by the interpreter, which is (() 5), as you would expect. For y...

Not as veratile as cormullion's match solution, but works for the given example:

Ah, that makes sense. Thanks, Lutz.

With:
we see the expected error:

ERR: missing argument in function max

I don't know why we don't see this with the + function, but the solution to both cases is to use curry:

Heh... I see, Cormullion. I felt that way about Perl before leaving her for Ruby (before newLISP and I met). Perl had a way of making you feel like a mad genius one day, and the village idiot the next. Jeffrey Friedl's Mastering Regular Expressions is a *really* good read. I highly recommend it. @hd...

Aw, come now, Cormullion... Regular Expressions are beautiful and powerful.

As with all regex engines, use anchors (like ^ and $) to restrict the match to start/end boundaries: > (regex {\d{3}} "12343243242") ("123" 0 3) > (regex {^\d{3}} "12343243242") ("123" 0 3) > (regex {\d{3}$} "12343243242") ("242" 8 3) > (regex {^\d{3}$} "12343243242") nil > (regex {^\d{3}$} "123") (...

Hi, Lutz,

In the last example box for (macro ...):
Trailing i a vim oopsie? :-)

Lutz, re: the manual entry for (macro ...)

1. The signature still has 'define' instead of 'macro'.
2. "But macro definitions cannot be repeated for the same symbol during the sane newLISP session." (sane)

Excellent. That should sort things out, one way or another.

@TedWalther: I'm honestly not sure *what* Ethereum _wants_ from newLISP. Perhaps that's something @janeTA can clarify. I had assumed though they they were happy with their VM/API and were looking for others to ratify their party.

Interesting observation, Lutz. That has helped me make a tech decision I've been pondering for a week or so now; thanks! :-) But I must admit I am still confused about newLISP's possible Ethereum interface. Surely if there was a newLISP interface, it would be... newLISP... right? The causal non-prog...

I was forced to experience Forth in uni by my most excellent computer architecture lecturer, Terry Anstey. I was too young and naive to value the experience at the time, but I have just recently decided to remedy that failing. newLISP needs a killer-app; I don't know if this can be it or not. Sadly,...

Hi, newlispers, I wrote a PEG (Parsing Expression Grammar) parser for Vim (https://github.com/dahu/Vimpeg) a while ago and recently ported it to newLISP (https://github.com/dahu/nlpeg). I would love for you guys to review my work. I am new to lisp and expect that I have made some boo-boos along the ...

@TedWalther Thanks for the getopts.lsp module, Ted. Here is a macro for combining the definition of short and long options into a single call. The aim here is to DRY up option specification. My newLISP-fu in general and macro-fu in particular is not strong, so please elucidate any boo-boos. ;; @synt...

You're tireless, Lutz! Awesome.
newLISP deserves a lot more attention; perhaps this move to the browser will help?

One thought I just had for this is to convert the newLISP manual example code segments into embedded, runable, modifiable, interactive learning tools.

Newlisp's (F)OOP Inheritance: (new Class 'Person) (define (Person:name) (self 1)) (define (Person:salary) 0) (new Person 'Worker) (define (Worker:salary) (self 2)) (setf people '()) (push (Person "John Doe") people) (push (Worker "Jane Doe" 3000) people) (define (describe person) (string (:name pers...

Wonderful. Thanks, Cyril.

newlisp has optional arguments (no need to point them out with a special keyword).
As I understand it, newlisp doesn't explicitly support keyword arguments although you could achieve a similar effect using association lists or hashes.

Excellent, Lutz. Those WP articles and the PDF helped a lot. Thanks! :-) Your example of handling separate concerns with contexts was clear. That reminds me of one of the GOF patterns... strategy? (I never got into the habit of quoting GOF patterns.) However, your example shows... completely separat...

Thanks, rickyboy! That helped a lot. I installed racket to see the difference. Hmm... This is premature of me to say so, but... I like the way newlisp does this better than racket. Which is to say... to my mind, that your are let ting x have another value before (g) is called, then it better show up...

Today, I believe that the problems with dynamic scoping are vastly exaggerated, which is sad, because people have stopped using dynamic scoping as a tool, exploiting its special characteristics, e.g.: switching and separation of concerns. Lutz... I would love to hear more about this. I am a struggl...

Hmm... Fair enough.

I see them as serving different purposes though. JSON is fine for machine-machine interfacing, but not well suited to human editing. YAML is much friendlier in that department.

Very nice. Any plans for doing the same for yaml?