Yes, I’m talking about Christmas gifts (or “winter solstice gifts” if you prefer) in July. I’m one of those people for whom buying Christmas gifts is a brain-wracking ordeal, and I’m always on the lookout all year round for the “perfect gift”.
Some people have inferred that I don’t write about .NET because I don’t like it. That’s not true. I use it myself.
The reason I don’t write about .NET is because I’m not an expert on it and there are plenty of other .NET blogs out there,
Murphy’s Law vindicated again. The Seattle Monorail has two trains, and last year they managed to collide. To get this to happen was particularly tricky, since the trains run on separate tracks, and there is only one spot on the entire line where a collision could occur—and they found it.
Reader Tom brought up the interesting point that ordinal-based imports are slightly faster than name-based, though not by much. But if even that tiny fraction of a percentage bothers you, you can still get the benefits of ordinal-based imports while still being name-based.
And you probably shouldn’t fall asleep in the van you break into.
How were DLL functions exported in 16-bit Windows?
How were DLL functions imported in 16-bit Windows?
How are DLL functions exported in 32-bit Windows?
Exported functions that are really forwarders
Rethinking the way DLL exports are resolved for 32-bit Windows
Calling an imported function,
When I wrote that the symbolic name for the imported function table entry for a function is called __imp__FunctionName, the statement was “true enough” for the discussion at hand, but the reality is messier, and the reason for the messy reality is function name decoration.
Hot off the presses. Real Madrid (with David Beckham, Ronaldo, and other stars) will play an exhibition match against D. C. United in Seah^H^H^H^HQuest Field on Wednesday, August 9th. I wonder if it’ll be anything like the last soccer match I saw.
Now that we’ve learned what the dllimport declaration specifier does, what if you get it wrong?
If you forget to declare a function as dllimport, then you’re basically making the compiler act like a naive compiler that doesn’t understand dllimport. When the linker goes to resolve the external reference for the function,
While it may be true that if you know Swedish, the world is funnier, I have to admit that my knowledge of German only served to create momentary confusion.
When I saw the headline that the head of BetonSports was arrested,