Bugfix kbemf set to 0 by default when not found

[sgiraz]

This PR enables the eomcParser to parse all parameters within TRQ_PID_OUTPUT_CURR, even if kbemf is missing.

cc @pattacini @Nicogene @isorrentino @DanielePucci

[DanielePucci]

Cc @GiulioRomualdi

[pattacini]

Thanks heaps for the fix @sgiraz
Just one inline comment to address.

[pattacini]

Thanks!
Awaiting the CI before merging.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[randaz81]

Is kbemf not used anymore? Then it's ok to have a default = 0. Otherwise I'd like to say that's a bad software practice to mix mandatory with optional parameters in the same parser block. In the long term things get confused, undocumented and In the past I have seen default value changing without any notice, leading to difficult-to-debug situations. For this reason, at least in yarp, the use default parameters is generally discouraged, and a revision of the configuration files to add the missing parameter is preferred.

[pattacini]

Hi @randaz81

Is kbemf not used anymore? Then it's ok to have a default = 0.

Indeed, kbemf is deprecated and already removed from the config files as per robotology/robots-configuration#599.