seqevent.cpp: bad switch statements ?

Bug #1229081 reported by dcb
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Seq24
New
Undecided
Unassigned

Bug Description

I just ran the static analyser "cppcheck" over the source code of
seq24-0.9.3

it said

[seqevent.cpp:562] -> [seqevent.cpp:564]: (warning) Variable 'result' is reassigned a value before the old one has been used. 'break;' missing?
[seqevent.cpp:564] -> [seqevent.cpp:566]: (warning) Variable 'result' is reassigned a value before the old one has been used. 'break;' missing?
[seqevent.cpp:606] -> [seqevent.cpp:608]: (warning) Variable 'result' is reassigned a value before the old one has been used. 'break;' missing?
[seqevent.cpp:608] -> [seqevent.cpp:610]: (warning) Variable 'result' is reassigned a value before the old one has been used. 'break;' missing?
[seqevent.cpp:625] -> [seqevent.cpp:627]: (warning) Variable 'result' is reassigned a value before the old one has been used. 'break;' missing?
[seqevent.cpp:627] -> [seqevent.cpp:629]: (warning) Variable 'result' is reassigned a value before the old one has been used. 'break;' missing?

Suggest add some break statements.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.