But I understand, that is not my point. You just need to add a clear example to the docs to make your point, because now you don't, everything is just old school string messages.
On 23 Feb 2014, at 18:41, Pharo4Stef <[email protected]> wrote: > > On 23 Feb 2014, at 13:32, Sven Van Caekenberghe <[email protected]> wrote: > >> >> On 23 Feb 2014, at 12:23, Norbert Hartl <[email protected]> wrote: >> >>> One of the core ideas is „logging objects and not strings“. >> >> I am missing a clear example of that though. > > > sven when opal is writing to the transcript that there is an undeclared or a > shadow I want to get a OPALCompilationLogEvent that I can query and ask to > jump in the broken code. > >> I am wondering what the expect interface is, how difficult/easy it is to fit >> in a new object as log (event). > > In SystemLogger you have > > self handleConvertedLogEvent: (self convert: aLogEvent) > > and convert: can do what ever we want to convert an object into a > string. > Stef > >
