From: Stefan S. <se...@sy...> - 2006-03-28 15:25:04
|
Tony Graham wrote: >>For the actual messages please keep in mind that these may be used for >>regression tests, so it would be good to avoid any runtime data such as >>process-ids, dates, etc. > > > glib puts in the process id. > > See the end of the generated 'testsuite/test.sh' in the 'testing' module for a > regex for stripping the process ids. I'm aware of that. That's why I ask. :-) I don't think the process id is particularly helpful here (and in most other contexts, for that matter). What is the advantage of using glib for that, as opposed to your own logger ? >>In fact, if these messages have some substructure (e.g. start with the >>line in the input at which the problem occured, it might be good to >>formalize the message structure to allow third party tools to develop >>parsers so xmlroff can be wrapped in a gui. (I'm thinking in particular >>of gcc's errors / warnings, and how these can be transformed into >>links in an emacs or eclipse console...) > > > The input line number has been lost (I think), especially if you started with > an XML file and an XSLT stylesheet. Right, I forgot about that. IIRC, libxml2 has some way to store line numbers in dom nodes, I'm not sure whether that would help to trace the context back though. > It's not that difficult to make xmlroff give an error message if you want to > see one for yourself. Ok. I'm aware that I'm talking about nice-to-have stuff here. Feel free to ignore it if it would be too hard to implement. It's just a usability issue that may come up later again. Regards, Stefan |