lua_map has a statement after a return which will never be executed

[Hans Joachim Desserud]

(Found by utils/create_cppcheck_report)

src/scripting/lua_map.cc:338 contains a statement after a return, which will then obviously never be executed. Since I don't know if the correct fix would be to remove it or place it in front of the return, I leave it to someone who knows what this code should do.

[SirVer (sirver)]

I just ran cppcheck 1.59 on this file and it did not report anything. Do I need to give it some flags? Assuming this is fixed/was a false positive and setting to invalid.

[Hans Joachim Desserud (hjd)]

Try with --enable=all :)

$ cppcheck --enable=all src/scripting/lua_map.cc
Checking src/scripting/lua_map.cc...
[src/scripting/lua_map.cc:337]: (style) Statements following return, break, continue, goto or throw will never be executed.
snip...

PS. Completely unrelated, but I've seen that cppcheck report 1.59 report a lot more unused functions in this file among others. Should probably be investigated to rule out false postives, though since I don't know exactly how this works I thought I'd ask: will some of the lua-related functions be only called from lua-scripts and not the c++ code so that they would show up as dead code?

[SirVer (sirver)]

There is no return to be found around this place in the code - I wonder what it means. This is a false possible to be sure.

yes, the lua methods would all show up as dead code in analysis, but they are all exercised from the test suite.

[SirVer (sirver)]

I must be drunk - this error is fixed now.

[Hans Joachim Desserud (hjd)]

>yes, the lua methods would all show up as dead code in analysis, but they are all exercised from the test suite.

I suspected something like that. There were a bit too many for it to sound like legitimate issues.

Thanks for fixing this error, btw.

[SirVer (sirver)]

Released in build-18 rc1.