unreachable and dead code

58 vues (au cours des 30 derniers jours)
VINAY
VINAY le 24 Fév 2026 à 4:25
Commenté : Fangjun Jiang il y a 5 minutes
why i am getting unreachable and dead code warning , i am not able to understant.
if anyone knows, please help me.
  2 commentaires
Image Analyst
Image Analyst il y a environ 9 heures
I can't even read that thing. What is that diagram? Is it Stateflow or Simulink (which I don't have)? How did you run your check on it? You might have some condition that is always false, like
value = false
if value
% Do something if value = true
% This block will never get executed since value is not a variable,
% it's a constant.
end
VINAY
VINAY il y a 12 minutes
Now you can check

Connectez-vous pour commenter.

Réponses (1)

Fangjun Jiang
Fangjun Jiang le 25 Fév 2026 à 14:06
Before the Simulink funciton Counter_Check1() is called, there is this operation "Cnt=Cnt+CntTime1". Then, inside the function, there is this comparison "Cnt>=CntTime1". Maybe due to the fact that the value of "Cnt=InitValue" is zero or positive, the comparison "Cnt>=CntTime1" is always true.
So the "{%Do Nothing}" transition is never reached. It might be okay in terms of the logic, but in terms of software, it is regarded as "unreachable" or "dead code". It is not a good practice to have unreachable or dead code.
Change the "InitValue" to be negative to see if the warning disappear.
  2 commentaires
VINAY
VINAY il y a environ 4 heures
hi @Fangjun Jiang i changed the "InitValue" To -ve eventhough warning is not dissppeared.
Fangjun Jiang
Fangjun Jiang il y a 5 minutes
You can attach your model here for others to try.

Connectez-vous pour commenter.

Produits


Version

R2022a

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by