Thanks for the tips! The trace seemed like it was more for lisp vs pilog but`I can see how that might help point you in the right direction (as much of the pilog is interpreted). Ok, so I could maybe put in a
(@ prinl " @X is " (-> @X)) as a rule clause as a debugging print. (And that would always succeed - because @ always unifies with the return value of prinl ... I think :-) --- On Sat, 6/25/11, Henrik Sarvell <hsarv...@gmail.com> wrote: From: Henrik Sarvell <hsarv...@gmail.com> Subject: Re: tracing pilog To: picolisp@software-lab.de Date: Saturday, June 25, 2011, 8:39 PM See trace, traceAll, lint, debug, $ and !. To be honest though, normally I just put a print statement. For me trace/traceAll have been useful on rare occasions where a variable should contain an object but it doesn't and I don't really know where in the code the problem is. A (trace ';) or (trace 'get) or if nothing else works a traceAll can give you good hints in those situations. On Sun, Jun 26, 2011 at 6:27 AM, Doug Snead <semaphore_2...@yahoo.com> wrote: What's the best way to trace pilog? I'd be interested in hearing how people go about debugging pilog programs. Doug -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
