All debugging in DBP is difficult which is why I implemented my own tracing code. If something doesn't work after I've written a new function I put some trace outputs.
` Create a trace file so as I can track various parts of the program
` Call this at the head of your program
function WL_TRACE_INIT(file$)
global WL_TRACE_FP as integer
c as integer : c=1
while ( c <= 32 and file open( c ) )
inc c
endwhile
if ( c <= 32 )
WL_TRACE_FP=c
else
exitfunction
endif
if ( file exist(file$) ) then delete file file$
open to write WL_TRACE_FP,file$
write string WL_TRACE_FP,"Trace file created : "+get date$()+", "+get time$()
write string WL_TRACE_FP,"File handle used : "+str$(WL_TRACE_FP)
endfunction
` call this at the foot of your program before 'end'
function WL_TRACE_CLOSE()
write string WL_TRACE_FP,"EOF Trace file (safe program exit)"
close file WL_TRACE_FP
endfunction
` use this to out trace of variables, etc
function WL_TRACE_WRITE(t$)
write string WL_TRACE_FP,t$
endfunction
As for the editor IDE, I tried codesurge and found I didn't like and went back to using the default editor. As for the built in debugger, erm, if it was ever useful, I've tried it and failed with it. I prefer doing my own trace debugging using the above code...
Warning! May contain Nuts!
