Re: Windows Assembly
- From: "f0dder" <f0dder_nospam@xxxxxxxxxxxxxxxx>
- Date: Tue, 13 Sep 2005 12:33:47 +0200
Philip Smith wrote:
> Where does this INVOKE thing keep coming from? Obiously the API calls
> require some kind of header file and whatever this INVOKE macro does,
> but I havent discovered where the header file is, or what this INVOKE
> macro does.
INVOKE is a masm builtin thing that does type + argument-count checking, and
handles pushing in the right right order (cdecl vs. stdcall) as well as
cleaning stack if necessary.
For the headers, either manually convert them from the PlatformSDK, or grab
the MASM32 package from www.movsd.com . Just stay away from the "masm32lib"
there, it's full of bugs and inferior code (and yes, this remark will make
hutch start another flamewar, but I don't care).
You might want to check out www.flatassembler.net as well.
> I haven't looked at anything much yet today. I did talk to a friend
> on the phone, and from that I think that I might download Dev-C++ and
> play with it for a while, and decide from there if I want to go with
> assembly or not. I think I can learn to live with what I hate about
> C.
Check out www.codeblocks.org and
http://msdn.microsoft.com/visualc/vctoolkit2003/ - it's a better combo than
Dev-C++ and GCC, IMHO.
> What would a Linux video driver look like? An X server? An SVGAlib
> compatible library?
Didn't they try to add that DRI stuff or whatever to the kernel?
.
- References:
- Windows Assembly
- From: Richard Cooper
- Re: Windows Assembly
- From: JGCASEY
- Re: Windows Assembly
- From: Richard Cooper
- Re: Windows Assembly
- From: JGCASEY
- Re: Windows Assembly
- From: Philip Smith
- Windows Assembly
- Prev by Date: Re: WaitForSingleObjectEx() is broken
- Next by Date: Re: Windows Assembly
- Previous by thread: Re: Windows Assembly
- Next by thread: Re: Windows Assembly
- Index(es):
Relevant Pages
|