On Fri, 24 Sep 2004, joe wrote:
> Again, there are valid uses of GetTickCount and there are safe ways of doing
> so. If there is concern, I do recommend testing functionality associated
> with each of the DLLs. You might find a bug you can report for kudos.
>
> On the incident, I would guess the vendor never had a clue it would do that.
>
>
> That function can't return more than 49.7 days without breaking every app
> that currently uses it. MS can not do that. That is why there is another
> function to get the info with a different datatype. See my other posts.
>
What seems to read clearly from your replies to this thread is that
either;
1> the code was better done under the original OS, unix
2> considering "how often" you seems to run into this same issue with
other coders in the windows realm, windows coders tend to be especially
lazy/clueless as compared to coders in other OS'
3> tools to code with in the windows realm are not as developed/functional
as they are in other envs
4> M$ does not properly provide developers with clued information with
which to do their jobs
>From which you can combine any or all of the above for a correct
interpretation of the total of your replies.
Thanks,
Ron DuFresne
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Cutting the space budget really restores my faith in humanity. It
eliminates dreams, goals, and ideals and lets us get straight to the
business of hate, debauchery, and self-annihilation." -- Johnny Hart
***testing, only testing, and damn good at it too!***
OK, so you're a Ph.D. Just don't touch anything.
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html
