Authored by: s65_sean on Friday, April 20 2012 @ 11:20 AM EDT |
And that would break nearly all of the legacy baggage that
windows
has.
Doesn't the legacy baggage itself break most of Windows
anyway?[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Friday, April 20 2012 @ 12:02 PM EDT |
DLL Hell arises because the API for the function library has changed and is no
longer compatible.
If the functions (signature, name, parameters) of version 1, are included in
version 2, and version 2 just adds a few extra functions, version 2 is a drop in
replacement (i.e you can dump version 1, and no one will notice).
Failure to design your API for long shelf like, failure to design a good API, is
a significant factor in the prevalance of DLL hell.[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Friday, April 20 2012 @ 12:03 PM EDT |
It's worse than that. Because of the way Windows works, about the only place
you can put a DLL you need is in the Windows directory. Otherwise it becomes
hard to access reliably. So everyone puts their DLL's in C:Windows.
Two DLL's have the same name, too bad. Need two different versions of the same
DLL. Too Bad.
I'll never forget the time upgrading MS Word killed all the mission critical
software on one set machines, even though MS Word had nothing to do with the
software they were running. The first question was, why was Word on those
machines in the first place.
[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Friday, April 20 2012 @ 08:55 PM EDT |
You have to go back a very long time for that to be true (probably to before
windows 95/NT). You've been able to use long names for DLLs for a VERY long
time and it doesn't break anything. There's winsxs since XP too, but that's
pretty nasty.[ Reply to This | Parent | # ]
|
|