What this means is that currently you could reference a non-existent 4D method in your code, but that code might not be executed because it is in an if/else/end if. In Active4D 2004 ALL code is checked for validity when the file is compiled, so this kind of situation will trigger a compile-time error.
This validation will only occur when the code is being compiled, right?
Validation also occurs during runtime for the cases where validity could not be determined at compile time.
So if a non-existent method is called at runtime in an if-else block, where the logic doesn't follow the non-matching conditional branch, then the error will still be noticed? Does this apply to other functional code or just to non-existent method calls? When could validation fail at compile time?
Regards Mark Howells
