thing. A routine to associate a file type with a program that does not
would have failed. Afterall, it failed to associate the file type with the
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
"Fail" is a strange metric in some cases.
For example, I once worked in a system where I created about 50 resource
elements (one per
file, each not more than 32K, the Win16 limitation). I gave them integer
IDs, 1..n (n was
between 47 and 54 depending on the data). My client complained that my
code was
"defective" because, when he ran it under Bounds Checker for Windows,
FindResouce would
"fail", and this was clearly a bug in the program. Of course, it was
HRSRC rsrc = ::FindResource(hlib,
MAKEINTRESOURCE(n),
MAKEINTRESOURCE(MY_RESOURCE_TYPE));
so OF COURSE it would fail when there were no more resources found in that
library! It
was *supposed* to fail! So it was hard to understand why he was upset
that the API would
fail. He also complained that ::LoadLibrary kept failing. The DLLs had
names like
DATA00.DLL, DATA01.DLL, ... so I just formed the name by adding 1 to a
counter and
generating the next DLL name and opening it, then iterating through its
resources, and so
on. So when I ran out of DLLs, I knew I had come to the end of the
available DLLs.
If an update had fewer DLLs, I could then use the VERSIONINFO information
and older DLLs
that were higher-numbered than the version of DATA00.DLL would be deleted.
So if the rule is that it succeeds as admin and fails silently without
admin, is it really
"failure"?
The real problem is the erroneous assumption that there can only be one
users per machine,
and the failures that accompany that flawed assumption.
joe
On Tue, 28 Oct 2008 09:27:27 -0600, "Jonathan Wood"
<jwood@softcircuits.com> wrote:
Tom,
It's unfair to say "doesn't work". It works if all of the conditions
are
right and the user is logged in as an administrator.
You know..., there are folks looking to write reliable code. Such folks do
not consider code that fails more often than it works as "working." I
think
it would be safe to put me in this category.
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm