On 22 April 2011 06:24, <csrabak@bol.com.br> wrote:
I disagree strongly. . . The transcript should maintain its purpose that is to show information 'intentionally' written to by the programmer.
and so, what if my intent is to show error stack trace on transcript? in headless mode i would prefer to log everything to some default logging facility.. guess which one? yes, it is Transcript. But then also i may want to use different stream for transcript in headless mode (to redirect output to stdout or file), but that won't require changing the error logging, which could simply output everything to Transcript.
If we feel the debugger info should be saved in some other place we should consider an alternate way of saving it, including, perhaps a log file and a {radio}button in the debugger itself.
My 0.19999999.....
Em 21/04/2011 15:19, Guillermo Polito < guillermopolito@gmail.com > escreveu: It should be fine to have stack traces into the Transcript as a default behavior in addition to the debugger.
Guille :)
-- Best regards, Igor Stasenko AKA sig.