can anybody tell me how to handle the EXTRN command with MASM32 :confused:
in TASM it's just: "EXTRN <name-of-api> : PROC"
i've tested that with MASM32, but it wouldn't work.
tia
in TASM it's just: "EXTRN <name-of-api> : PROC"
i've tested that with MASM32, but it wouldn't work.
tia
Hello,
I am also having some trouble with some sintaxes in MASM... maybe I didnt find the right place yet, but if you do, please tell me where can I get it too!! ;)
I have only 1 idea for you now: check on the Icz tuts ( tut 17 uses dll's :) and also the examples... I think you may find a template of what you want there... I have had some sucess too, by searching things in the win32 API reference...
I have reading a little through win32.hlp, the help files with MASM32 ( in help dir ) and also Iczelion tuts and some alien code too... although I am having some trouble with it, since it is not as commented as I d'like it to be...
Anyway, luck for us! And smartness too!! ;)
See ya'round.....
Almost detached question: aren windows' APIs external calls??
I am also having some trouble with some sintaxes in MASM... maybe I didnt find the right place yet, but if you do, please tell me where can I get it too!! ;)
I have only 1 idea for you now: check on the Icz tuts ( tut 17 uses dll's :) and also the examples... I think you may find a template of what you want there... I have had some sucess too, by searching things in the win32 API reference...
I have reading a little through win32.hlp, the help files with MASM32 ( in help dir ) and also Iczelion tuts and some alien code too... although I am having some trouble with it, since it is not as commented as I d'like it to be...
Anyway, luck for us! And smartness too!! ;)
See ya'round.....
Almost detached question: aren windows' APIs external calls??
I'll check after work, but I belive:
EXTERN HeapAlloc:PROC
should work. no <>
EXTERN HeapAlloc:PROC
should work. no <>
externdef stdcall FuncName :proto stdcall :dword, :dword
ploptor,
Get used to the idea that MASM and TASM are different, MASM uses libraries and prototypes and if you do this normal stuff, you will have no problems with MASM at all.
Use the syntax,
INCLUDE myfile.inc
INCLUDELIB myfile.lib
This give you both the prototype and library and you can use any function in the library that way.
Regards,
hutch@movsd.com
Get used to the idea that MASM and TASM are different, MASM uses libraries and prototypes and if you do this normal stuff, you will have no problems with MASM at all.
Use the syntax,
INCLUDE myfile.inc
INCLUDELIB myfile.lib
This give you both the prototype and library and you can use any function in the library that way.
Regards,
hutch@movsd.com
i know about include and includelib. actually i was trying to implement a call to vbasic functions, e.g. vbaInputBox. (--- call me nuts 'cos of that, but i mean it ---)
and as we know, there are no includes for visual basic. or am i wrong?
and as we know, there are no includes for visual basic. or am i wrong?
i know about include and includelib. actually i was trying to implement a call to vbasic functions, e.g. vbaInputBox. (--- call me nuts 'cos of that, but i mean it ---)
and as we know, there are no includes for visual basic. or am i wrong?
Hahahahahahahahhahahaa..... sorry, serious: why? :)