Extending proc macro with "public"

Index > Macroinstructions > Extending proc macro with "public"

Author

Thread

alorent

Joined: 05 Dec 2005
Posts: 201

alorent

Hello guys,

By default all our procs are "private" to our .asm module. We have to put "public OurProc" to make it public.

Would it be possible to extend the proc macro to accept "public" when we define our proc? Example:

Code:

myProc proc PUBLIC param1, param2

 ....

myProc endp

Thanks!

31 May 2010, 17:12

revolution
When all else fails, read the source

Joined: 24 Aug 2004
Posts: 17476
Location: In your JS exploiting you and your system

revolution

Extending proc to do that would be quite easy. In much the same way that stdcall and c are detected you can add public.

But, of course, it would only work with linkable output formats.

31 May 2010, 17:16

Tyler

Joined: 19 Nov 2009
Posts: 1216
Location: NC, USA

Tyler

Is there a way to tell what format is being used, like an internal variable or something? Kinda like % can be used to get the number of the current iteration of a "repeat."

31 May 2010, 20:48

baldr

Joined: 19 Mar 2008
Posts: 1651

baldr

Tyler,

No, AFAIK. In most cases one can check for low $$ symbol value to detect COFF, but this is unreliable. (?)

31 May 2010, 21:10

alorent

Joined: 05 Dec 2005
Posts: 201

alorent

Thanks revolution.

I have been trying to extend the proc macro but cannot get it to work Sad

Well, with my lack of knowledge in macros... Smile

I mean, I want that the "public" word can be added or not and not just make all procs public.

Any help?

01 Jun 2010, 08:59

revolution
When all else fails, read the source

Joined: 24 Aug 2004
Posts: 17476
Location: In your JS exploiting you and your system

revolution

You can try to add this to PROC32.INC:

Code:

...
   match =params, params \{ params equ statement
                      flag = 0 \}
; ADD vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
   match =PUBLIC args, params \{ params equ args
                         public name \}
   match =PUBLIC, params \{ params equ
                   public name \}
; ADD ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   match =uses reglist=,args, params \{ regs equ reglist
                                 params equ args \}
...

I have not tested it. But it should be able to give you a starting point to work from.

01 Jun 2010, 09:10

alorent

Joined: 05 Dec 2005
Posts: 201

alorent

Thanks revolution!

I have checked it but unfortunately, the proc is not made public. The "PUBLIC" after proc is accepted by the assembler with your modifications, but the "public name" directive does not seem to make effect.

Code:

TestProc proc PUBLIC param1
   
    fffffff   ; this should produce error
    ret 

TestProc  endp

The above is compiled correctly. Only when I put explicitly "public TestProc" the assembler gives error on "ffffffff" line.

Thanks

01 Jun 2010, 12:08

revolution
When all else fails, read the source

Joined: 24 Aug 2004
Posts: 17476
Location: In your JS exploiting you and your system

revolution

alorent wrote:

Code:

TestProc proc PUBLIC param1

Try with the fasm syntax.

Code:

proc TestProc PUBLIC param1

01 Jun 2010, 12:17

baldr

Joined: 19 Mar 2008
Posts: 1651

baldr

alorent wrote:

Only when I put explicitly "public TestProc" the assembler gives error on "ffffffff" line.

If function label is unused, function body is skipped altogether.

01 Jun 2010, 12:34

alorent

Joined: 05 Dec 2005
Posts: 201

alorent

Thanks a lot guys! Smile

02 Jun 2010, 09:22

< Last Thread | Next Thread >

Forum Rules:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum