Deactivation switch for implicit expansion
4 visualizaciones (últimos 30 días)
Mostrar comentarios más antiguos
Matt J
el 29 de Dic. de 2016
Comentada: Digital Guy
el 28 de Sept. de 2021
4 comentarios
Jan
el 7 de En. de 2019
Maybe running the code and exhaustive unit-tests in R2016a is the best option for debugging. It will not only reveal implicit expansion problems, but all other incompatibilities with older software also. Unfortunately this requires a conservative programming style, e.g. to avoid modern strings defined with double quotes.
Respuesta aceptada
John D'Errico
el 20 de Feb. de 2018
Editada: John D'Errico
el 20 de Feb. de 2018
I believe it is not possible to disable the expansion. Personally, I like having it, just that people don't like change. There is some risk in implicit expansion, in that MATLAB novices will sometimes get hurt.
Now, could they introduce a settable flag, telling MATLAB to not use expansion? Yes, they surely could do so. The problem is then code written is no longer portable. Move your code to another computer that has the flag set off or on, and suddenly your code will not work. Or if your code sets the flag and someone uses your code, then suddenly you may have effectively introduced a bug into their code.
So, sorry but IMO, a flag or preference that can disable expansion is a bad idea.
Could you disable it yourself? I suppose you could overload the affected operators, checking for any case of implicit expansion. If you find it, then trap out with an error, saying that implicit expansion is just wrong in your humble opinion, and you won't allow it to work on your system. If no expansion is detected, then use the built-in operator. Yes, it will slow down your code. But it would work.
7 comentarios
Chuck37
el 29 de Abr. de 2019
I just recently moved up to 2016B and implicit expansion is a nightmare. I write quick and dirty code for analysis and am getting burned by this. I'm not a "novice" at MATLAB by any stretch, but I have become accustomed to letting error messages guide me on trivial row vs. column situtations. I just spent an hour figuring out why I was getting the wrong answer from norm(a-b). It turns out, of course, that matlab was blowing a row/column mismatch out into a matrix. Ugh.
Digital Guy
el 28 de Sept. de 2021
These comments are spot-on, and exactly what I have encountered from my viewpoint as another "novice" who has used Matlab for >20 years.
Más respuestas (1)
Jan
el 19 de Feb. de 2018
I'm convinced, that there is no switch to disable it. Otherwise it would have been mentioned in the forum.
7 comentarios
Ver también
Categorías
Más información sobre Historical Contests en Help Center y File Exchange.
Productos
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!