fcnTest.m is a file that the user is writing out in the course of calculations. The point was to show how to, and how not to, write a new file out during the course of calculations so that it could get recognized and used later in the processing.

mode is controlling whether you clear or use exist to see if the function fcnTest is available. And you might use both.

id was used in the commented version of fcnBug so you could tell whether version 1, 2, 3, or 4 was the one being found (versus what you might expect).

To understand more details, which are a bit nuanced (and clearly I haven’t shown them well here), you could try experimenting with the code yourself. The nuances come from how you run the function and therefore get different results. If you run in the debugger, all is well. If you run in the normal fashion, you get issues because the file was cached and MATLAB doesn’t recognize there’s a new version without some intervention. clear is the way to go, but it matters where/when you perform the clear.

The main thing to notice is the use of clear near the top of the repaired function. That is the key to getting the new code recognized under all the different circumstances.

–Loren

Anyway, I’m surprised that no one commented on this.

The topic title seems attractive, but I can’t follow anything about this.

What is the function fcnBug suppose to do? I’m guessing this is just to illustrate some subtle detail regarding the path precedence. But, I can’t figure out what the expected results of this function are.

What are the id & mode variables controlling?

Also, what is this fcnPuzzle?

And, where us this fcnTest.m? What does it do?