#418: ruby: base/Vector3d inconsistency
----------------------------+-----------------------------------
Reporter: Alexander.Duda | Owner: rock-dev-mailing-list
Type: defect | Status: new
Priority: major | Milestone:
Component: base | Keywords:
----------------------------+-----------------------------------
base/Vector3d is the only type of all base/VectorVectorNd having a ruby
extension which introduces a problematic inconsistency when accessed from
ruby:
my_type.vec3d.x = 123 # OK
my_type.vec3d[0] = 123 # OK
my_type.vec3d.data[0] = 123 # Fails silently
The reason for this is that vec3d.data only returns a local copy of the
data stored in vec3d
which get modified but this change is never reflected by the real type.
This is counter intuitive as all other VectorNd types can be modified in
this way because of the missing ruby extension.
my_type.vec4d.data[0] = 123 # OK
--
Ticket URL: <https://rock.opendfki.de/ticket/418>
rock <https://rock.opendfki.de>
rock: the robot construction kit
_______________________________________________
Rock-dev mailing list
[email protected]
http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
