While at it, it would be good to touch on the "interpreter only" approach of PicoLisp. It is objectively simpler than an interpreter AND compiler implementation. However, I would love for some expansion on the explanation of "True equivalence of code and data". Also, is there any update to the view on performance in the context of new machines.
Would it be possible to record these? Regards, Kashyap On Wed, Nov 4, 2020 at 8:32 AM Alexander Burger <a...@software-lab.de> wrote: > Hi Alex, > > > For me the greatest obstacle in using picolisp is the lack of arrays. > Let's > > talk about what I'm doing wrong and why I don't need them! > > Yes, good idea. This is a valid and common question. > > Maybe, as a warm-up, you could also check "Array Abstinence" at > > https://picolisp.com/wiki/?arrayabstinence > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >
