Talk:DOM guide: Error handling
- Just making sure--there's only one version active at a time, so if you've already registered one and then register another, you don't have to do anything about removing or unregistering the previous one as far as the DOM is concerned? (other than freeing any memory that the old one used, which I gather the DOM doesn't itself know about or care about? What I mean is, if you didn't do your deletes as shown in the example & just registered a new one, it would work ok?)
- The error & warning functions are already implemented in the default if you just want to use the default?
- You say that "A client application is free to call the daeErrorHandler code to route its error messages." If an app elects to just use its own code and not use the DOM facility, I assume that there are still messages that the DOM itself sends through the handler?
Elf 11:44, 27 March 2007 (PDT) Ellen:
- The DOM will manage the memeory for the default error handler. Its only if you create and use your own you need to manage that object. There is no unregistering. If you want to use a new one just call setErrorHandler with the new one.
- Yes they print to the C standard error stream.
- Yes the DOM routes it's internal error messages through daeErrorHandler, whether or not the client app uses daeErrorHandler for it's errors.
Alorino 12:07, 27 March 2007 (PDT)