> From: Kevin King > It's funny, our subroutines are oddly similar to how > Microsoft implemented DLL wrecknology for Windows, but > we've never had the kind of hell that Windows > programmers experience. Funny how that works... :)
I completely disagree. Have you never been working on code in a live shop, make a change, and have someone in the other room scream? Errr, neither have I, but Hypothetically... DLL Hell is where you change a subroutine on which many others are based, and where calling programs are unprepared for a change in behaviour or structure of the called program. Since we operate in a global environment, where all users in an account share the same calling and called programs, we're subject to the exact same issues. Try changing a common block without recompiling all the programs that Include it, or adding an argument to a subroutine without changing the programs that call it. Welcome to the MV version of DLL Hell. ..NET addresses DLL hell by allowing calling programs to call a specific version of the subroutine, so updates with a different version don't cause the callers to blow up. We could do this in MV too but I don't know anyone who does. The way we do it is to set flags in the code that route differently based on port number or user name or something similar. When the code is fully debugged we remove the flag and all users execute the same code, hopefully without error. That wrecknology has been fixed. Programs that continue to break aren't making use of the wrecknology, errr, the current features. MV has yet to catch up. T _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
