Explore >> Select a destination
|
You are here 
|
gpfault.net | ||
| | | | |
www.cs.virginia.edu
|
|
| | | | | ||
| | | | |
erikmcclure.com
|
|
| | | | | It's been known for a while that windows has a bad habit of eating your exceptions if you're inside a WinProc callback function. This behavior can cause all sorts of mayhem, like your program just vanishing into thin air without any error messages due to a stack overflow that terminated the program without actually throwing an exception. What I didn't realize is that it also eats assert(), which makes debugging hell, because the assertion would throw, the entire user callback would immediately terminate without any stack unwinding, and then windows would just... keep going, even though the program is now in a laughably corrupt state, because only half the function executed. | |
| | | | |
samwho.dev
|
|
| | | | | How does a function in Ruby call a function in C? How does a function in Kotlin call a function in Java? It's no secret that you can call functions in one progr... | |
| | | | |
ericlathrop.com
|
|
| | | This weekend I gave a presentation on the Jekyll static site generator at MOSSCon. | ||
