; This project aims to build a binary FORS(R) capable to execute or compile
;text input from keyboard or file. Typical commands for the build are shown
;in lines 6 to 13 of forsr.asm file - in submitted forsr.zip archive.
; As an aid for the builder to include /leave out parts of the source file,
;I wanted to add a reference table to the compilation output, showing how
;often each function has been called by any other. This reftable is the
;very topic of this blog.
; The following additions have been made to file forsr.inc : 
virtual at 0
refs::
 dw 0 dup  16
 dw 0 dup 128
 dw 0 dup 400 
end virtual
; This array size reflects the current size of FORS. A theoretical limit
;would allow for 2^15-1 function-calls=refs, so entries would need only
;15 bits for ref-count, and the msbit can be used to flag the functions'
;invisibility (to users of FORS).
; FORS functions (during build process) are FASM symbols of 4 characters.
;These may be referred to as the assembly or meta name, as parameter 'nam'. 
;When a function 'myfc' is defined, its array location will be named 'rmyfc'.
;There are 2 macros, P and H, for function definitions. P uses assembly code,
;these functions do not make references and are placed before all H-made
;ones, which are mere lists of references to P- and other H-functions.
; The number of P-functions is currently limited to 14+2spare+128, while the
;set of H-type ones is, assisted by reftable, managed by the builder and,
;to a lesser degree, the user. 
macro h nam,..{;here restricted to reftable functionality.
a#nam: name equ nam
nam=expression($)
r#nam=288+pt*2;pt is a global variable
pt=pt+1;prepare for next definition
}
;If myfc is being referred to, refs:rmyfc must have 1 added to for any ref.
;If myfc is to be invisible, H must set the sign bit of refs:rmyfc .
;Both operations are implemented by:
macro ixr xa,xi=1{;increment refs:xa
 if defined `xa
 load xd word from refs:xa
 store word xd+xi at refs:xa
 end if }
; However, H-functions may be refered to before being defined!
;This is the reason why we use assemblers, and especially FASM,
;which excels in symbol resolution and macro features.
;But all load and store instructions such as in IXR
;raise "error: value out of range". The only sensible reason for
;this message is that xa would be undefined or outside the array.
;The FASM 1.72 Programmer's Manual suggests to use "assert 0",
;but this did not provide an improvement. Instead, I used
irpv n,name { display 10
 forward
 if defined r#n
  display `n,32
  p4 r#n
 end if
}
;at the end of forsr.asm . This, I think, makes sure that all
;assembly names and their associated r#n labels are defined.
; When every call of IXR is commented out (in file forsr.inc) the
;compilation succeeds and the printout shows all assembly names,
;and their labels are present and correct. So my question is:
;???   IS THERE ANY (FORMAL) ERROR in REFS: or IXR   ???
;PLEASE EXPLAIN why loads and stores to refs: do not work!!!
; The files, as described before (reftable defined, initialized,
;r#n labels defined and printed at the end of file forsr.txt)
;have been combined into archive FORS.ZIP .

;The following macro PR, was planned to be called as last activitiy of
;compilation to to get the final result, as promised by comment:
macro pr {;print table of all reference counts
;?  Is it correct to use "r\#n" and "\}" ?
 irpv n,name
  if defined r\#n
   if r\#n in <0,32,288>
    display 10
   else
    display 32
   end if
   display `n,32
   load xd word from refs:r\#n
   display xd/8000h*2+'+'
   pz xd mod 8000h
\} }
; PR uses an equivalent load command as IXR and calling it would show
;the same error message. But I tried printing "experimentally" in some
;undocumented ways, there were partial results:
- The numbers were always shown as 0, even when initialized >0.
- The "in" condition was never true (no linefeeds printed to separate
  the "subranges"). As if 0, 32, 288 had never occured!    

x=1
if x in <1>
 display 'x = 1',0xa
end if    

flat assembler  version 1.73.31  (16384 kilobytes memory)
1 passes, 0 bytes.    

x=1
if x = 0 | x = 1
 display 'x=0 or x=1',0xa
end if    

flat assembler  version 1.73.31  (16384 kilobytes memory)
x=0 or x=1
1 passes, 0 bytes.    

virtual at 0
refs::
 dw 16 dup 0
 dw 128 dup 0
 dw 400 dup 0
end virtual    

Code:

virtual at 0
refs::
 dw 0 dup  16
 dw 0 dup 128
 dw 0 dup 400 
end virtual
    

So my question is:
;??? IS THERE ANY (FORMAL) ERROR in REFS: or IXR ???
;PLEASE EXPLAIN why loads and stores to refs: do not work!!!

virtual at 0 as 'refs'
refs::
 dw 16 dup 0
 dw 128 dup 0
 dw 400 dup 0
 sizeof.refs = $
end virtual    

macro ixr xa,xi=1 {;add refs:xa xi
 if ~ defined xa
  display 10,9,`xa,' undefined!',10
 else if xa < sizeof.refs
  load xd word from refs:xa
  store word xd+xi at refs:xa
 else
  display 10,9,`xa,'('
  temp = 1
  while temp < xa
   temp = temp * 10
  end while
  while temp <> 1
   temp = temp/10
   display '0' + ((xa/temp) mod 10)
  end while
  display ') out of bounds!',10
 end if
}    

revolution:
I do not think we disagree. My code (... in<0,16,288>) was intended to detect 1 of 3 values ...

I understand why this happens (tjzp is not yet defined at this time) but as I understand the resolving policy of fasm, it should take note of this fact and resume later. (As we humans know, the action of ixr does not even need new memory space, the word to be incremented is at refs:0046h .

virtual at 0
refs::
 rb 2+sizeof.refs
end virtual    

irpv n,name { common temp = 0
 forward
 if r#n > temp
  temp = r#n
 end if
} sizeof.refs = temp