Inside SWT

Monday, October 16, 2006

Windows 64-bit

I'm currently working with Grant Gayed, porting SWT to Windows 64. Some smart guys from Intel submitted a great patch (57151). However, each line of code needs to be painfully checked. Why?

"Every line is sacred, every line is great ..."

Ok, the real reason: it's easy to make subtle mistakes and cause GP's. We found only a few so far (because those guys did such a great job). Anyway, during our travels, we got to see the Windows API again and I forgot how funny some of it was. Here are a few things we ran across:

#define TECHNOLOGY 2 // bet you didn't know that!

typedef enum tagFUNCKIND {
FUNC_VIRTUAL,
FUNC_PUREVIRTUAL,
FUNC_NONVIRTUAL,
FUNC_STATIC,
FUNC_DISPATCH,
} FUNCKIND // FUNCKIND kids these days!

BOOL InitCommonControlsEx(
const LPINITCOMMONCONTROLSEX lpInitCtrls
); // Horny little devils

STGC_DANGEROUSLYCOMMITMERELYTODISKCACHE = 4
// What the ?!?!

Steve

6 Comments:

  • hee hee, snicker, giggle.

    By Blogger Wayne, at 9:47 PM  

  • You've got to be careful what you put these days ...

    http://www.theregister.co.uk/2006/10/13/code_outrage/

    By Blogger AlBlue, at 3:03 AM  

  • Al ... hilarious!!

    By Blogger Steve, at 4:21 AM  

  • Steve, you'll love this:
    http://www.google.com/codesearch

    Type in any BS and sure enough there's code out there that contains it.

    Like this:
    http://www.google.com/codesearch?hl=en&lr=&q=mofos&btnG=Search

    "we "leak" memory like mofos"

    UFB, Steve

    /adam

    By Anonymous Anonymous, at 9:29 PM  

  • Is this done yet? I need it for Android development

    By Anonymous Anonymous, at 10:43 PM  

  • Um ... yes. The bug report in this blog is fixed. If you go to the Eclipse.org download page, it's there ...

    By Blogger Steve, at 7:49 AM  

Post a Comment

<< Home