[Pharo-dev] Logging API discussion

Denis Kudriashov dionisiydk at gmail.com
Thu Apr 28 08:29:27 EDT 2016

2016-04-28 11:07 GMT+02:00 Tudor Girba <tudor at tudorgirba.com>:

> > Put you logging api in a Trait instead of Object and let your
> MySpecialDomainObject use this trait ?
> >
> > Really?
> > Try remember usual workflow when we investigate some problems with code
> when we can't use debugger. We put kind of "Transcript show:" in multiple
> places to see state of our objects at concrete point of time. With object
> logging we will log our objects directly without converting to strings. Do
> you want to stop your "debugging workflow" every time you need to log
> objects which not support it? (to add special trait).
> This is a totally different scenario than the one of logging for an
> unforeseen situation. For this purpose, in Beacon we have dedicated signals
> such as those that capture the stack or the context and we can imagine
> several more. It is more powerful than Transcript and requires no string.
> Furthermore, because we have the type signal, we can also easily have an
> inspector that shows the relevant information.

I hope you not think that I suggested to log strings. I never did it. I
proposed to log domain objects instead of signals with ability to annotate
them with additional information.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20160428/ac041bf1/attachment.html>

More information about the Pharo-dev mailing list