D
dbeavon
Guest
I'm assuming you are deliberately creating a scenario where the parameter "a" is replacing another variable with the same name (that is already scoped to the outer procedure)? If the parameter to the function ("a") is renamed to "x" then would the problem go away? It seems like you are asking for trouble if you use overloaded meanings of a variable name, as you do in this example. You've probably spent some time at this. What happens if the datatype of "a", in the function, is switched to an integer. Is the compiler less confused when there are totally different datatypes involved? Is the problem specific to longchar or does it happen with character variables? What about if you have a FORWARD declaration of the function that is declared *before* defining the variable in the outer procedure ("def var a as longchar no-undo.").
Continue reading...
Continue reading...