Ask Learn
Preview
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Via Larry Osterman's recent series on concurrency, I ran across an older post from Raymond Chen on why you shouldn't use reserved fields in internal Windows data structures.
About ten years ago, when I was working on the QuickTime team at Apple, we got a report from a beta tester about some third-party application that was completely broken with the new version of QuickTime. Several hours of debugging in MacsBug later, I discovered that the problem came from that application using a reserved field in the heap data structures. In that version of QuickTime, we had included a patch to the memory manager to work around a problem in older OS versions. That patch needed to use the reserved field, which obviously conflicted with the third party app's use of that field.
When I sent the vendor an email about this, the response came back: "But you can't use that field; it's reserved!"
Umm ... yes.
Anonymous
April 03, 2005
Blog link of the week 13
Anonymous
July 01, 2005
Because they changed.
Anonymous
November 27, 2007
PingBack from http://feeds.maxblog.eu/item_314913.html
Anonymous
June 08, 2009
PingBack from http://cellulitecreamsite.info/story.php?id=8620
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign in