On Wednesday 19 November 2003 17:02, Ulrich Mayring wrote: > Niclas Hedhman wrote: > > Guys, remember Ulrich doesn't do UnitTesting at all, so he need the > > container to enforce the accuracy of his code. He assumes that the > > component writer is an idiot, who doesn't know how to code and need all > > the UnitTesting to happen in runtime ;o) > > The container is responsible for calling the lifecycle methods in the > correct order. Don't know what that has to do with unit testing. It has > a lot to do with coding conventions in a multi-developer team. Maybe you > guys work on your components all by yourself, but we have 9 people using > each other's components, so standards are very important.
I was implying that you want an external party to enforce the component developer to "configure before starting threads", and all the other execution requirements of the component. Some people here would say, the component writer already knows which order things must be executed, and if that is violated (by mistake for instance), the unit testing would catch it. Cheers Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
