On Thu, Jan 26, 2017 at 11:35:20PM +0100, pd wrote:
> Alex, thanks a lot for your very clarifier reply (specially the procedural
> way of thinking which makes a lot of sense to me), I'm still confusing in a
> couple of things...
No problem!
BTW, I thought again about the terminology of "list"
Hi Dean,
> i.e. I'm calling m1 from m2 using the same syntax as calling methods
> externallybut just replacing *Obj with This.
Yes, that's fine.
> No problem if not butIs there a shorter way e.g. like (: member)
> instead of (get This 'member)
Yes, (: member) is the same as (get This
Alex, thanks a lot for your very clarifier reply (specially the procedural
way of thinking which makes a lot of sense to me), I'm still confusing in a
couple of things...
I've read in docs that the ' prefix in a name of formal parameter when
describing a funcion indicates it's a evaluated
i.e. I'm calling m1 from m2 using the same syntax as calling methods
externallybut just replacing *Obj with This.
No problem if not butIs there a shorter way e.g. like (: member)
instead of (get This 'member)
(class +Clss)
(dm T ())
(dm m1> () (setq Res 4))
(dm m2> (Arg2) (+ (send
Hi Pd,
>- three base data types: Numbers, Symbols and Cons Pairs (Lists),
>...
> suggesting dotted pairs are the same as lists, both are
> indistinguishable so it should be possible to write any list as a dotted
> pair, i. e. (1 2) = (1 . (2 . NIL)) but what is the list for (1 . 2)
I was reading the picolip documents ref, tutorial and function reference
and I'm afraid I misunderstand some concepts, so I'm asking a bunch of
questions in the hope you can help to achieve a better picolisp
understanding
1- In the ref document it's said talking about types in picolisp:
-
