Preprocessor behaviour (bug?)

Index > Compiler Internals > Preprocessor behaviour (bug?)

Author

Thread

LocoDelAssembly
Your code has a bug

Joined: 06 May 2005
Posts: 4633
Location: Argentina

LocoDelAssembly

Look at this code

Code:

macro macro     {display "It is a macro"} ; No error at this point
macro struc arg {display "It is a struc"} ; No error at this point

struc struc{display "It is a real struc"} ; Does not invoke the macro struc above


a struc ; displays "It is a real struc"


struc ; Error: invalid name.
macro ; Error: invalid name.

Shouldn't fasm do throw error immediately instead of allow definition of macroses that will not be callable later?

10 Jul 2007, 23:44

vid
Verbosity in development

Joined: 05 Sep 2003
Posts: 7105
Location: Slovakia

vid

looks like nice catch Smile

11 Jul 2007, 01:35

cepers

Joined: 23 Jul 2007
Posts: 1
Location: MBIT.NET

cepers

ehhhmm.... Very Happy

23 Jul 2007, 21:40

LocoDelAssembly
Your code has a bug

Joined: 06 May 2005
Posts: 4633
Location: Argentina

LocoDelAssembly

haha, thanks to cepers I remember that I forgot to tell that it actually happens with all the preprocessor directives. In the case of "common", "reverse" and "forward" it works well but if you call a macro with any of those names inside a macro the preprocessor will not call the macro but will interpret it as directive instead.

23 Jul 2007, 21:59

LocoDelAssembly
Your code has a bug

Joined: 06 May 2005
Posts: 4633
Location: Argentina

LocoDelAssembly

bump

09 Jul 2008, 15:09

revolution
When all else fails, read the source

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

revolution

Is this really a bug? It seems that if someone tries really hard to completely confuse themselves by doing this then they deserve all they get. Wink

This seems more like a way of winning an obfuscation contest than writing real code.

09 Jul 2008, 16:25

Tomasz Grysztar

Joined: 16 Jun 2003
Posts: 7845
Location: Kraków, Poland

Tomasz Grysztar

Is fixed for 1.67.28.

I'm un-stickying the threads with bug reports that already have resolved (even though the new version is not released yet). This helps me trace what is left to do, please do not make them sticky back.

09 Jul 2008, 16:26

LocoDelAssembly
Your code has a bug

Joined: 06 May 2005
Posts: 4633
Location: Argentina

LocoDelAssembly

Quote:

Is fixed for 1.67.28.

Sorry for asking but, what are the news for the 1.67.27 version then? Razz

Quote:

This helps me trace what is left to do, please do not make them sticky back.

Good method Smile

But note that I haven't make it sticky and I believe that it wasn't sticky when I bumped it. I had made sticky only the REPT bug.

09 Jul 2008, 22:05

Tomasz Grysztar

Joined: 16 Jun 2003
Posts: 7845
Location: Kraków, Poland

Tomasz Grysztar

LocoDelAssembly wrote:

Quote:

Is fixed for 1.67.28.

Sorry for asking but, what are the news for the 1.67.27 version then?

Ooops. I guess I forgot to release it. Very Happy

09 Jul 2008, 22:29

Tomasz Grysztar

Joined: 16 Jun 2003
Posts: 7845
Location: Kraków, Poland

Tomasz Grysztar

OK, I will rename it back to 1.67.27 then. Twisted Evil

10 Jul 2008, 07:31

DOS386

Joined: 08 Dec 2006
Posts: 1901

DOS386

Tomasz Grysztar wrote:

LocoDelAssembly wrote:

Quote:

Is fixed for 1.67.28.

Sorry for asking but, what are the news for the 1.67.27 version then?

Ooops. I guess I forgot to release it.

COOL

Please look at the other BUG's: FASMD page fault, $0200-MZ bug (trivial) also Wink

_________________
Bug Nr.: 12345

Title: Hello World program compiles to 100 KB !!!

Status: Closed: NOT a Bug

11 Jul 2008, 08:04

Tomasz Grysztar

Joined: 16 Jun 2003
Posts: 7845
Location: Kraków, Poland

Tomasz Grysztar

I just realized it was not really so good idea to disallow using names of preprocessor's directives in ALL cases of defining preprocessor's symbols, because this way it included the FIX directive. This example from fasm's documentation:

Code:

    macro tmacro [params]
     {
      common macro params {
     }

    MACRO fix tmacro
    ENDM fix }

is no longer working because of this "fix". I'm correcting it for the next release (1.67.29).

08 Nov 2008, 14:11

< 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