On 10/10/08 16:17, Thorsten Ziehm wrote:
You are right in that point, that the developer needs a tool, which show
him easily if his code changes work fine. In first step this could be
done in development environment. But the final approval of the changes
must be outside of the development environment.
Why?
1. You cannot identify dependencies which are working in development
environment only. If you do not have such dependencies (perhaps link
to special libs or something else) the code could break and show an
error in the implementation (tests).
2. Code isn't submitted into the code management system, but it is in
the development environment of the developer. The problem can be
found only, when the code is build and executed outside this
environment.
Both scenarios aren't so rarely.
But as I wrote above. This tooling should also work in the development
environment. But it shouldn't run in this environment only.
I agree. (And re Martin's question where the disagreement is: It was
indeed only the "make" issue. Sorry if I caused any confusion.)
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
