Solving the gcc 4.4 strict aliasing problems

A couple of days ago Jeff Stedfast ran into some problems with gcc 4.4, strict aliasing and optimizations. Being a geeky sort of person, I found the problem really interesting, not only because it shows just how hard it is to write a good, clear standard, even when you’re dealing with highly technical (and supposedly unambiguous) language, but also because I never did “get” the aliasing rules, so it was a nice excuse to read up on the subject.

Chrome and Moonlight, or how to deadlock a browser

It’s no secret that Moonlight works best on Firefox at the moment - it’s our baseline browser, after all - but we’ve had many requests to add Chrome support, and since it supports NPAPI just like all browsers out there, it should really work out of the box, requiring only some extra code to implement/hackify stuff that Chrome/WebKit doesn’t expose and that we need - basically, DOM support and some downloader tweaks.

Now where did I put my type?

Today I ran across an interesting problem while trying to export a function from a dll built in vc++ (2003). I’ve been digging into the mozilla source a lot lately, doing the library to embed mozilla and get our much-needed webcontrol working on Mono, and after a successfull browser window invocation from .net (screenies to come soon) (woohoo), I decided to clean up the code a bit and start doing the functions properly.

.NET Bugs Registry

.NET Bugs Registry Nice handy list for those weird things that can bite you when you least expect it…

NumericUpDown is a nice control... eh

NumericUpDown Bug From the site: FAQs NumericUpDown How do I get the Tooltips to be shown on a NumericUpDown control? This is because of a bug in the .NET Framework. When tooltips are set on a control that hosts other controls within it (like the NumericUpDown), tooltips are not shown on those child controls. To workaround this issue, do the following in code: [C#] foreach ( Control c in numericUpDown1.