On Thu, Dec 16, 2021 at 12:20 AM pd wrote:
> This way the syntax and behaviour in picolist is not internally
> coherent, every function application must be a list but for quote, which
> can be not a list but an improper list.
>
> Maybe I'm misunderstanding something.
>
> indeed the example in p
Hi pd,
> - it breaks compatibility with almost all lisp out there
> ...
> Maybe I'm misunderstanding something.
Perhaps, though at a deeper level.
First of all, forget other Lisps! I always say it is best if you start with
PicoLisp without knowing "Lisp". Lisp dialects differ a lot, but PicoLisp
On Thu, Dec 16, 2021 at 6:35 AM Danilo Kordic
wrote:
> Hi pd
>
> It seems You are looking for Wikipedia/Currying . What are Your further
> thoughts?
>
No I don't
>
> What do You think about Wikipedia/De_Bruijn_index ?
>
I think it's an interesting proposal for using with lambda calculus
Hi pd,
On 16.12.21 10:17, pd wrote:
> : (quote (quote (quote a)))
> -> (quote (quote a))
In which practical use case do you ever need such an abhorrent nesting
of quotes?
If you need ''a or even a in code, then I strongly suspect your
software design is not appropriate for the speci
Thanks for your explanation, Alex
On Thu, Dec 16, 2021 at 10:24 AM Alexander Burger
wrote:
>
> First of all, forget other Lisps! I always say it is best if you start with
> PicoLisp without knowing "Lisp".
>
:) That's a nice advice but sadly I feel I can't do that ;-)
> The term "improper l
On Thu, Dec 16, 2021 at 11:51 AM wrote:
>
> In which practical use case do you ever need such an abhorrent nesting of
> quotes?
>
it's not a question of practical use but compatibility and tradition, also
a question of semantics
> But I'm having doubts about this being not just a superficial th
Hi,
McCarthy’s "A micro-manual for Lisp" in 1978 lists 10 rules as the core of LISP.
The first rule states the behavior of QUOTE. If you select a different set of
rules,
you get a different LISP.
In picoLisp QUOTE is defined differently.
Regards,
Andras Pahi
> On 2021. Dec 16., at 12:17, pd
On Thu, Dec 16, 2021 at 12:09:03PM +0100, pd wrote:
> On Thu, Dec 16, 2021 at 10:24 AM Alexander Burger
> wrote:
> > First of all, forget other Lisps! I always say it is best if you start with
> > PicoLisp without knowing "Lisp".
>
> :) That's a nice advice but sadly I feel I can't do that ;-)
On Thu, Dec 16, 2021 at 03:37:50PM +0100, Alexander Burger wrote:
> 'quote' simply does nothing, and '+' ignores an atomic CDR.
>
> And not only '+', but every built-in I can think of.
To be more clear: I'm talking of *evaluated* arguments. That is, I don't know
any function of the form (fun . 'a
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, t
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* jus
On Thu 16 Dec 2021 at 21:48, Alexander Burger wrote:
> 'quote' is the mother of all functions. It does nothing, and just returns
> Args.
> No need for "special forms"!
Because there is no concept of compiler.
Compilation in picolisp is done ahead of time manually in another
language.
--
UNSUBS
12 matches
Mail list logo
