At one level of abstraction, calling a function normally is equivalent to pulling out the function header and setting up the parameter list, and then using eval on the code.
eval() and evalin() are not somehow emulating code: they use the normal internal expression tokenizer, getting back a parse tree, which is submitted to the execution engine. This is not just "like" how matlab executes functions and scripts: it is how matlab executes functions and scripts.
Thus, evalin() processes the same way the line of code would be processed intthat environment (except possibly details of caching), so it would give whatever result that code would. Which is to say that copy-on-write is used, which provides references to variables.
