yarp::os::Value constructors should be explicit

Created on 2 May 2018  路  3Comments  路  Source: robotology/yarp

These constructors

    Value(int x, bool isVocab = false);
    Value(double x);

allow to do evil things, I believe they should be explicit, forcing the user to call Value constructor when assigning stuff.

Unfortunately this is a breaking change, and I believe that this is used in several places outside YARP (and in YARP unit tests).

YARP v2.3.72 Library - YARP_os YARP v3.0.0 API Bug Fixed BreakinBehaviour Change

Most helpful comment

I'm in favor of making them explicit!

All 3 comments

I'm in favor of making them explicit!

Was this page helpful?
0 / 5 - 0 ratings