[Pharo-project] Why errors are not logged in the Transcript?

Guillermo Polito guillermopolito at gmail.com
Fri Apr 22 15:28:22 CEST 2011

Maybe I'm to viced by other techs, but reading and sharing the stack trace
is a common task in everyday work.  And I think the transcript as a "log
console" and useful only for debugging purposes....

And putting info into files is not the smalltalk way... BTW, I hate
searching for the stacktraces into the PharoDebug.log :P

On Fri, Apr 22, 2011 at 1:24 AM, <csrabak at bol.com.br> wrote:

> I disagree strongly. . . The transcript should maintain its purpose that is
> to show information 'intentionally' written to by the programmer.
> 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 at gmail.com >
> escreveu:
> It should be fine to have stack traces into the Transcript as a default
> behavior in addition to the debugger.
> Guille :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20110422/dd729524/attachment.htm>

More information about the Pharo-project mailing list