First a quick note, I'm on holiday at the moment with my only wifi access being the occasional mcdonalds. Sorry if I don't reply immediately.

I want to create a lookup table for use within a procedure (using the win32a includes proc macro). It worked when I was not using a procedure. I have tried:
• Using the procedure name as a label, so MyProc.Label etc
• using a global label within the procedure, and also that with the proc name prepended

Thanks for any help, I could declare the lookup table inside the procedure (after the term statement would be easiest) but it's a pain that it doesn't work as I would expect.

Matt Diesel

you mean

mmm, odd, you should be able to define a label like ".LUT:" and use it (which would be also accessible from outside using procname.LIT), however, if it still fails then put at the beginning of the source "dummy = procname", just in case that conditional compilation is screwing things up (but everything should be OK if the LUT is accessed from the proc only).

Please post some minimal code showing the problem.

Thanks guys, i have been testing on a small sample but I'm posting from an iPhone at the moment. Off the top of my head it's:



That won't compile as the iPhone capitalises thinking it's helping.

I'll post the exact code when I get the chance. It shouldn't matter that the proc is defined after the usage as my understanding of the fast multiuser system is that order of definition doesn't matter.[/code]

MattDiesel, then if your code above is accurate enough, your problem is that you are accessing the internal label directly but never accessing the main label (testProc). Since proc macro uses conditional compilation, you don't get defined your ".lbl:" and nothing inside the proc because there is no reference to testProc. As I've told you earlier, use "dummy = testProc" to cause a reference to be detected and force the conditional compilation to include the proc's code (note that "dummy = testProc" incurs in no run-time costs as it is a compile-time only thing).

what if you do this

Placing this macro after including the include files will disable conditional compilation (and I hope it won't introduce problems)

typedef, it doesn't even compile when "y" is referenced.

^^@lol... I didn't try it at all I just thought of it. .. Well we learned something there

Thanks LocoDelAssembly, conditional compilation being the problem would make sense, though I had no idea that fasm had it though so it never occured to me.

I will try the dummy method and see if that works. It's not ideal as there is a reason I'm going for a lookup table rather than cmp ... je.

Matt