Bind common names can cause execution errors
- What: In a macro that has an include file I have found that if I have multiple binds that call subroutines in the include file, the parser will choose the wrong subroutine in the include. In this particular instance, I had /ExFolYX and /ExFolYXZ as binds in my macro. In my include file the YXZ subroutine was second, and if I called the first bind, it would go to the second subroutine every time, even though it was supposed to match the first subroutine. I have attached a simple macro and include file. If you run the macro and execute the bind /exfolyx 0 0 it will still call the second sub in the include file, including the echos for it although the bind clearly says to call the first subroutine in the include file.
- How: Unclear, but appears to be using a partial match method perhaps to find the subroutine?
- When: If you have bind execute calls that are very similar, but not quite the same.
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information