Hi
I'm used to sprinkling print statements in my code as a way of tracking
down bugs but they seem to be affecting my code more than I was expecting.
I've also realised I'm never quite sure when and when I shouldn't precede a
symbol with a quote e.g. as a function argument in a (debug 'Symbol)
stat
Hi Dean,
> I'm used to sprinkling print statements in my code as a way of tracking
> down bugs but they seem to be affecting my code more than I was expecting.
I recommend to look at 'trace' and 'msg'. They both output to stderr and don't
interfer with the expressions.
'trace' shows what argumme
Hi,
I'd like to subscribe to your maillist :)
Thanks!
Raimon Grau
--
blog -> http://puntoblogspot.blogspot.com
My my, I see it! Thanks Alex.
On Thu, Dec 8, 2016 at 1:50 AM, Alexander Burger
wrote:
> Hi Bruno,
>
> > I've written something that redefines T to NIL, which surprises me
> > because I thought that T was protected from redefinition like that, and
> > I have not found a command in the code that l
Did you 'lint the source code? 'lint should warn you when you have T as
Parameter in a function.
2016-12-09 5:51 GMT+01:00 Bruno Franco :
> My my, I see it! Thanks Alex.
>
> On Thu, Dec 8, 2016 at 1:50 AM, Alexander Burger
> wrote:
>
>> Hi Bruno,
>>
>> > I've written something that redefines T t
Hey Dean,
I think that, in general, you want to quote a sym argument to a function
when
you want to change the value of that symbol. For example:
: (setq A 1) # Set the value of A to 1
-> 1
: (inc A) # Evaluate A, *then* pass the result to inc
-> 2
: A
-> 1
: (inc 'A) # P
