mgrier's WebLog
learn.microsoft.com/en-us/archive/blogs/mgrier
Windows internalsOS / kernelSoftware / engineering practiceMicrosoft blogsMSDN archive
- Posts
- 33 from 10 Feb 2004 to 2 Oct 2006
- Posting
- archived, read-only
- Kind
- personal blog
- Feed
- https://learn.microsoft.com/en-us/archive/blogs/mgrier/feed.xml
2006 1
2005 28
- The NT DLL Loader: FreeLibrary()
- The NT DLL Loader: DLL_PROCESS_ATTACH reentrancy - wrap up
- The NT DLL Loader: DLL_PROCESS_ATTACH reentrancy - step 4 - ramifications of questionable quality
- The NT DLL Loader: DLL_PROCESS_ATTACH reentrancy - step 3 - quality requirements
- The NT DLL Loader: DLL_PROCESS_ATTACH reentrancy - step 2 - GetProcAddress()
- The NT DLL Loader: DLL_PROCESS_ATTACH reentrancy - step 1 - LoadLibrary()
- The NT DLL Loader: reentrancy - play along at home!
- The NT DLL Loader: DLL callouts (DllMain) - DLL_PROCESS_ATTACH deadlocks
- The NT DLL loader: dynamic unloads
- How the NT Loader works
- Enough about in-memory models and transactions for now
- Transactions and in-memory data (part 3 of n)
- Transactions and in-memory data (part 2 of n)
- Transactions and in-memory data (part 1 of n)
- No Chinese Dictionaries
- More than one way to skin a (transactional) cat
- Implementation patterns to support transactional functions
- Local vs. global analysis revisited
- Whole program vs. local analysis
- Working with inexact error contracts
- Even good design can't succeed in isolation
- Why is fclose()'s contract so confusing?
- What if close could fail?
- Function transactionality
- Side-effects: a more useful definition
- Errors and a simple invariant
- Always check your return codes?
- Future examples - standards, conventions