Because using it leads to exactly this kind of error: impossible to bug fix. Because beginners think eval solves all of their problems, and so they stick it everywhere, and then get stuck with bugs like this. Because using eval removes all of the inbuilt code-checking that highlight syntax errors and give warnings about mistakes. Because eval is a poor tool for solving basic problems like this. Because eval is slow and pointless in this use case. Because eval obfuscates code intentions. Because you cannot click on those variables and let the editor show you their values, and highlight where they occur in the code. Because function tab-completion and dynamic help menus do not work with eval. Because instead of letting MATLAB help you to write your program, eval makes it more difficult. Because eval is an awful construct for assigning to variables. Because even the documentation clearly states that eval should be avoided:
"Code that calls eval is often less efficient and more difficult to read and debug than code that uses other functions or language constructs"
And now there is a bug that is hard to locate and debug... because of eval.
That is the error.
