Re: Why print statement should determine whether I get an error or

On Fri, Dec 9, 2016 at 7:58 AM, Bruno Franco wrote: > P.S. > I'm still new to picolisp, so don't take any of what I say as gospel. And if > anyone > can confirm or expand on what I've said, I'd appreciate it a lot. I'm not a veteran but let me expose what I once

Re: Why print statement should determine whether I get an error or

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) #

Re: Why print statement should determine whether I get an error or

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

Why print statement should determine whether I get an error or not

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)