How to skip error and continue (NOT in loop)?
16 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
n33
am 5 Apr. 2019
Kommentiert: Walter Roberson
am 11 Mai 2023
If I have the following code, how to display x(10) after x(9999) causing an error?
x = ones(1, 10);
try
x(1)
x(9999)
x(10)
catch ME
fprintf(ME.message)
end
The output I got is:
ans =
1
Index exceeds the number of array elements (10).
Thanks!
0 Kommentare
Akzeptierte Antwort
Walter Roberson
am 5 Apr. 2019
x = ones(1,10);
idx = [1 9999 10];
for K = 1 : length(idx)
try
x(K)
catch ME
fprintf(ME.message)
end
end
8 Kommentare
Steven Lord
am 11 Mai 2023
A = command1thatcanpossiblycauseanerror;
B = command2thatcanpossiblycauseanerror;
C = command3thatcanpossiblycauseanerror;
D = command4thatcanpossiblycauseanerror;
% etc
That has a similar code smell to the frequently asked question about dynamically creating variables with numbered names like x1, x2, x3, etc., for which the general consensus is to avoid doing that.
Rather than posing a hypothetical scenario, can you share a little more detail about your actual application where you use a pattern like that code? What do those commands that can possibly throw an error do? Are they independent or are the outputs of one or more of those functions the inputs to later of those functions?
Walter Roberson
am 11 Mai 2023
I am having difficulty thinking of any code that is such that
A = command1thatcanpossiblycauseanerror;
is valid code, but
for dfpSzcGKKqyMbgIcvYXqkicEiRRKtIUpb_vjDshBQupYrSfhm_GS_xNidaex = 1 : 1
A = command1thatcanpossiblycauseanerror;
end
"cannot" work.
The only things I can come up with are along the lines of "needing" dbstack to be able to pinpoint the function name... ummm, no, even that would not explain things.
Weitere Antworten (0)
Siehe auch
Kategorien
Mehr zu Startup and Shutdown 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!