some_var = 0

a_label:

        jmp .sublabel

if some_var = 1

        include 'test2.asm'

end if

        .sublabel:       

        display 'This should not be opened'

        another_label:

        err 'This should not be built'
                                                       

SOME_VAR EQU YES
match =YES,SOME_VAR {
  ...
}
match =SOME_VAR,SOME_VAR {
  ...
}
    

It is not a bug.

if 0
  \1:
end if
.1:
rb 16; make some noise
\.1 = .1; make it accessible inside '\1' scope
\1 dw \.1, \1.1
.1:    

rept 0 {
  \1:
}
.1:
rb 16; make some noise
\.1 = .1; make it accessible inside '\1' scope
\1 dw \.1, \1.1
.1:    

shutdownall wrote:

It is not a bug.

I disagree. Probably fasm handles labels too early (I'm going to examine sources, but not too soon).

As a side note, presence of SOME_VAR equ SOME_VAR is indistinguishable from its absense.

match =FAST_MODE,STARTMODE {
        CDFLAG  db FAST_MODE
}
match =SLOW_MODE,STARTMODE {
        CDFLAG  db SLOW_MODE
}
match =STARTMODE,STARTMODE {
        CDFLAG  db SLOW_MODE
}
        assert  CDFLAG > -1
    

As shown above, other constructs appear to have no effect in test2.asm; only the jmp is assembled if another_label is removed.

Consider the following:

Code:

if 0
  \1:
end if
.1:
rb 16; make some noise
\.1 = .1; make it accessible inside '\1' scope
\1 dw \.1, \1.1
.1:    

One could expect that it will compile, but it doesn't. Next one compiles fine:

Code:

rept 0 {
  \1:
}
.1:
rb 16; make some noise
\.1 = .1; make it accessible inside '\1' scope
\1 dw \.1, \1.1
.1:    

cod3b453 wrote:

As shown above, other constructs appear to have no effect in test2.asm; only the jmp is assembled if another_label is removed.

Well look at your sample in the first posting.
The reason why the jump fails is simple.
You make a jump to a local label 'sublabel'.
This is valid in the own context 'a_label'.

If you include your code, a new main label 'another_label' is defined and so 'sublabel' becomes a sub label of 'another_label'.
That's the trick.

But you can still jump to this label from the other code with jmp another_label.sublabel for example. But it is not a good coding style to include another file in this main label routine. At the end of 'a_label' would be a nicer place, don't you think so ?