News:

MASM32 SDK Description, downloads and other helpful links
MASM32.com New Forum Link
masmforum WebSite

Update *.inc files by yourself

Started by Rockphorr, October 19, 2006, 04:26:16 PM

Previous topic - Next topic

Rockphorr

I recomend to all users of masm32
1) mov all directives "include X.lib" fom the project asmfile to X.inc file (sample: include kernel32.lib to kernel32.inc)
2) replace PROTO to PROTO STDCALL
3) change .MODEL FLAT,STDCALL to .MODEL FLAT

So you can control the name decoration directly and create your prolog and epilog.
Samples:

_Some@12 PROC NEAR PUBLIC
;prolog instructions
.....
;epilog instructions
                   ret   12
_Some@12 ENDP
;-------------------------------------------------------
_Some1@12 PROC EXPORT
;prolog instructions
.....
;epilog instructions
                   ret   12
_Some1@12 ENDP
Strike while the iron is hot - Бей утюгом, пока он горячий

Vortex

The Win32 API system uses the STDCALL calling convention, why to replace all those PROTO STDCALLs with bare PROTOs? Specifying decorated names doesn't seem to be a nice solution for normal programming.

Ehtyar

I'd have to agree with the comment about includelib at the bottom of inc files, that never really made sense to me why that isnt done..but as far as everything else goes, all i can say is....no :U

Rockphorr

Quote from: Vortex on October 19, 2006, 04:58:08 PM
The Win32 API system uses the STDCALL calling convention, why to replace all those PROTO STDCALLs with bare PROTOs? Specifying decorated names doesn't seem to be a nice solution for normal programming.
Sometime i need the abnormal or exotic style of a programming. This "PROTO STDCALL" is a way for me to link a standard INC of LIB & DLL.
Strike while the iron is hot - Бей утюгом, пока он горячий