Odd behavior with a Simulink reserved name in a function?
3 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
Jim
am 19 Jul. 2017
Bearbeitet: Walter Roberson
am 15 Okt. 2017
Not sure what to make of this. Running R2017a. I have a numeric double precision variable named f14n. I save it to a .mat file. I call a function that loads the mat file with variable f14n in it, and it becomes a Simulink model. This of course crashes the function because I'm treating f14n as a numeric variable. Threw together some ugly code (below) to reproduce what I'm describing. Variable f14n is fine in the calling script, but it launches a Simulink window in the function. Is this a bug or am I breaking a bunch of scripting rules here? Thanks.
f14n=1:10;
save junk.mat f14n
x=10;
dum=junk_func(x);
%%%%%%%%%%
function dum = junk_func(dum2)
load junk.mat
f14n
dum=0
0 Kommentare
Akzeptierte Antwort
Steven Lord
am 19 Jul. 2017
Don't "poof" variables into the workspace like that. When MATLAB parsed junk_func it needed to know to what f14n referred. Since there was no indication in the code that it was a variable, and there is a Simulink® model available by that name, it treated that reference as opening that model.
Weitere Antworten (0)
Siehe auch
Kategorien
Mehr zu Configure and View Diagnostics finden Sie in Help Center und File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!