On 23 Feb 2014, at 14:30, Norbert Hartl <[email protected]> wrote: > > Am 23.02.2014 um 14:07 schrieb Sven Van Caekenberghe <[email protected]>: > >> >> On 23 Feb 2014, at 14:01, Norbert Hartl <[email protected]> wrote: >> >>> >>> Am 23.02.2014 um 13:32 schrieb Sven Van Caekenberghe <[email protected]>: >>> >>>> >>>> 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. I am wondering what the >>>> expect interface is, how difficult/easy it is to fit in a new object as >>>> log (event). >>> >>> The „message“ instVar in Log is supposed to be any object not just strings. >>> So the easiest way to „log“ your object is >>> >>> myObject asLog emit >>> >>> What it does is to wrap a Log class around myObject being the message then. >>> The creation of the Log class is dispatch through myObjects class so every >>> business object can decide its own preferred log vehicle which can act as a >>> bridge between special log objects and common log behavior. >>> >>> Does that answer your question? >> >> More or less, I think I understand. Is this what you do yourself or is that >> how SystemLogger works ? What I meant is that this needs to be added to the >> documentation since it is so crucial to the 'not strings but real objects' >> mantra, and right now it is not explained well. >> > This is how SystemLogger works. > So this is missing in the documentation? I need to read again and will add > this. It won’t just be the next days because I’m on vacation then.
By explained I mean, an example, all the examples now are with plain strings...
