Re: [Gnumed-devel] review of possible checkin.

[catmat]

Ian Haywood wrote:

> catmat wrote:
>
> >  >                       else:
> >  >                               print "icon for ", png_fname, " is 
> > not ok"
> > 128a143
> >  >                       print "trying to add page", self.plugins[i]
>
> Again, use gmLog
>
>
> Ian

it's easier to use print statements, and then disable them with # after
debugging the module :
the reason is that the log becomes so full, it's difficult to discern the
section one is trying to debug. The #print statements can be later
removed , or changed to logging if there is long term value in keeping
the debugging statement around.

 Yes there are log levels, and possibly filtering of logging based on 
originating module, but I haven't worked out how to do that at the 
configuration level ,environment level or  the command line level ( is 
it documented?).
One of the main reasons development is so slow is there is no step through
debugger, or the technique for using one is not widely known, and that
debugging via the log is so painful because the technique for log  filtering
is not widely known. Maybe the howto for debugging should be in the wiki.
The howto should be more concrete than just guidelines, "one should use
LogException() because it prints out a stacktrace in the log where the path
to an exception can be traced through line numbers in each module file."

Is anyone using a tool/editor that can link a log files  path  
statements to  a
editor to auto-open the module file concerned at the line number?
(maybe one should be written).

gmEMRBrowser also seems to have print statements for debugging.