Index
> Windows > [SOLVED] Why c:DWORD does not compile? |
| Author |
|
|
baldr 06 Nov 2010, 13:08
Picnic,
Are you afraid of "New thread" button? 
proc is a macroinstruction. By default, its arguments are separated by commas (yes, function name is argument too). Macro can parse arguments further, as defined by specification. This is the cause of your problem: «SomeProc c:DWORD» argument is split into «SomeProc» (name for function), «c» (calling conventions tag) and «:DWORD» (as a somewhat weird function parameter's name). |
|||
06 Nov 2010, 13:08 |
|
|
Picnic 06 Nov 2010, 13:23
Ok but why c:DWORD cause trouble but a:DWORD compiles fine?
Quote: Are you afraid of "New thread" button? Not at all, i have no means to damage primer topic  |
|||
|
06 Nov 2010, 13:23 |
|
|
revolution 06 Nov 2010, 13:27
proc abc stdcall vars,...
proc abc c vars,... proc abc vars,... Code: proc SomeProc stdcall:DWORD |
|||
|
06 Nov 2010, 13:27 |
|
|
baldr 06 Nov 2010, 13:40
revolution,
Perhaps Tomasz should change calling conventions' tag to «cdecl» to avoid name clash. |
|||
|
06 Nov 2010, 13:40 |
|
|
revolution 06 Nov 2010, 13:43
Or «ccall» and «stdcall» to match the macro names. With maybe aliases «cinvoke» and «invoke» also.
|
|||
|
06 Nov 2010, 13:43 |
|
|
Picnic 06 Nov 2010, 13:54
Oh i understand, thanks baldr & revolution. shame on c
 |
|||
|
06 Nov 2010, 13:54 |
|
< Last Thread | Next Thread > |
Forum Rules:
|