Hi Chrostophe and Alex
Thank you very much for your adviceIt is very timely.
I'm only too aware of the dangers of using setq, having been bitten a few
times now by interference between functions in my whole program.
I'm tending to develop functions in isolation so I can watch them like a
Hi Alex
Thank you for the adviceI've just this minute used debug by
coincidence...but not with breakpoint and I've never used trace.
so thank you for those and also for putting me straight re the positioning
and syntax of (let (A 1 B 2..
Please have a good rest of the weekend.
Best Regards
I've just tried sprinkling (!) in my source.
That is going to help me A LOT. It looks like the PL equivalent of int 3 :)
On Sat, Jan 28, 2017 at 09:55:14PM +0100, pd wrote:
> Thank you Alex for your patience, I see I have a severe confussion about
> how picolisp manages lists
No problem! It is good to discuss this here, as it may help others too.
> let's start by the begining... as far as I know (f a b 4) is
Hi Dean,
> I'm tending to develop functions in isolation so I can watch them like a
> hawk.
Watching like a hawk is always good! ;)
In addition to that, I would recommend to use 'trace' and 'debug'. Especially
'trace' is more useful than it may seem, letting you monitor your whole
program's
If we take objects as an example...You might want to use these to create
static variables using object properties which you want to persist within a
limited scope. You might setq the object itself to make it persist but do
you manipulate the objects properties (that you want to persist) using setq
