Ok as I don't think my teacher would appricate me callint it that, one is a more proper name for DLL hell?
Ok as I don't think my teacher would appricate me callint it that, one is a more proper name for DLL hell?
I shall call egypt the harmless dragon
-Isaiah 30.7
that depends on what you mean by dll hell. The fact that you don't like them?
"You are stupid! You are stupid! Oh, and don't forget, you are STUPID!" - Dexter
DLL Maintenance Issues
complexities of dynamic linking
problems with dlls
dlls hurt my rear
"You are stupid! You are stupid! Oh, and don't forget, you are STUPID!" - Dexter
>>> DLL hell
It is the term in common use by the industry. Why would any teacher worthy of the title insist on calling it something different.
Wave upon wave of demented avengers march cheerfully out of obscurity unto the dream.
DLL Linkage Descrepencies
In industry, call it anything you like but don't use words like bug, fault, error, failure, problem and hell.
>>> call it anything you like but don't use words like bug,
!
Why do you use the word "bug" to denote a programming error?
Wave upon wave of demented avengers march cheerfully out of obscurity unto the dream.
Because if I use the term 'programming error', then it's my fault the program doesn't work. But if I say it's bug, then I can explain that it must have just crawled in over night and has nothing to do with me.
More sersiously, software customers often raise 'wish lists' of new features as bugs. I.e. "RID51-02 : the software does not have button to formulate a theory of gravity." I wouldn't want these classed as programming errors.
Where ever I've worked, the company normally has it's own term for bug/error. Stuff like:
Review Item Descrepency (RIDs)
A non-comformity
Item of non-compliance
etc. etc.
"requested feature"
"You are stupid! You are stupid! Oh, and don't forget, you are STUPID!" - Dexter
New M$ Standard.
globalerr_h
Win98se
Dev-C++ 4
Borland55 with JFE
