this has been driving me nuts for a while and I finally found out what’s going on:
first define mymacro has a root level macro, then:
cc /sometable
mymacro
will tell you that mymacro is not found
cc /someCOMP
mymacro
will work fine
this has been driving me nuts for a while and I finally found out what’s going on:
first define mymacro has a root level macro, then:
cc /sometable
mymacro
will tell you that mymacro is not found
cc /someCOMP
mymacro
will work fine
Is there any reason why you’d want to cc into a non-COMP? Seems like we should disable that to avoid bugs like this popping up.
Let me know if there is a reason why you need to do this.