Hi Alex,
Op di 31 jul. 2018 om 17:34 schreef Alexander Burger :
>
> But 'cut' is *not* a destructive function. It does not modify the list in
> any
> way. Only the variable which points to the list is modified.
>
OK. That isn't totally obvious, but of course you are right as shown per
this examp
Hi Arie,
I agree with everything you wrote, except:
> 1. mutability. Operations like 'cut' alter the contents of their
> argument(s). So, it is very important to understand that in PicoLisp
> 'functions' often are not functions in the mathematical sense, because
> there arguments would never be c
Hi Bruno,
1. mutability. Operations like 'cut' alter the contents of their
argument(s). So, it is very important to understand that in PicoLisp
'functions' often are not functions in the mathematical sense, because
there arguments would never be changed by a function. For e.g. a Scheme
programmer
On 31.07.2018 07:41, Bruno Franco wrote:
three questions:
1) Which clashed with your previous experience as a programmer?
The pilog part, I stopped thinking about transferring Prolog LPN
examples when it came to Prolog list handling ([head | tail]) or
Context Free Grammars /Definite Clause Gra
three questions:
1) what parts of picolisp have you had trouble understanding? Which clashed
with your previous experience as a programmer?
2) What features of picolisp are you using right now? Did you learn
something interesting while using them that you would like others to know?
3) is there a
