Thanks for the suggestion Joe.
Other than copy-paste examples, I haven't played much with either #oop and
#dbase in picolisp. It is definitely on my list ;)
I've been trying to get a good understanding of variable scope, state and
lifetime. Especially with functions that have the side-effect of
m
Hi Lindsay,
It looks like you are using job primarily to retain the value of N
between invocations. Is that true? Just curious, why not move the loop
inside of hexSpigot instead of looping outside of it? Another option
to consider if you want the behavior of being able to increment the
hexSpigot a
Hi Lindsay,
> I'll have to play with your solution a bit. I don't quite follow how the
> global is working there in conjunction with 'job and 'off.
There is nothing mysterious about it.
'job' evaluates its first argument. So there is absolutely no difference whether
you quote that argument
(
Thanks Alex,
I'll have to play with your solution a bit. I don't quite follow how the
global is working there in conjunction with 'job and 'off.
However, after banging around on this for a couple of hours, trying 'copy',
various auxillary functions to return the quoted 'job, etc I was at my wits
Hi Lindsay,
> (de hexSpigot NIL
>(job '((N))
> ...
> : (do 32 (prin (hexSpigot)))
> ...
> 0123456789ABCDEF0123456789ABCDEF-> "F"
> ...
> : (pp 'hexSpigot)
> (de hexSpigot NIL
>(job
> '((N 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12
> 11 10 9 8 7 6 5 4 3 2 1 0 ) )
