From: Martin B. <mar...@gm...> - 2005-07-08 04:19:57
|
On 7/7/05, Felix Wiemann <Fel...@gm...> wrote: > Martin Blais wrote: >=20 > > The reporter is used at parsing, transform and writer stages. > > Conceptually, it seems to me that the publisher should be responsible > > to create and own the reporter and pass it along to the various stages > > for perusal. >=20 > When inserting system_messages, the system_message node class isn't > instantiated directly but reporter.info/warning/error/severer() is > called. So separating reporter and document would not make things > easier; you'd virtually have to pass a reporter every time you pass a i'm wondering how much trouble that is (havent't had time to look yet). > document. And after all I think there is a 1:1 relation between > reporter and document. So, while it may not seem entirely clean, the document tree relates to "the representation of the document". the reporter relates to "the process of running" a parser / reader / writer / transform. for example, you could have two writer/transforms running on the same shared document structure, with two separate reporter instances associated with these two processes. |