-
Key: RLS-81
-
Legacy Issue Number: 14004
-
Status: closed
-
Source: JARA ( Shuichi Nishio)
-
Summary:
Fig5,Fig9) RoLo Symbolic Position class and RoLo Position class are specified to be 'union' but it is better to leave them unspecified. 'Union' is hard to implement for some programming language
-
Reported: RLS 1.0b1 — Thu, 18 Jun 2009 04:00 GMT
-
Disposition: Resolved — RLS 1.0
-
Disposition Summary:
Stop using ‘union’ as suggested in the summary, For the C++ PSM, as we found
that some compilers are unable to treat ‘union’ with elements that owns
constructors, we will also stop using union and make the elements as pointers.
Implementers need to be aware that only one of the elements shall be effective. -
Updated: Fri, 6 Mar 2015 20:58 GMT
RLS — Fig5,Fig9) RoLo Symbolic Position class and RoLo Position class
- Key: RLS-81
- OMG Task Force: Robotic Localization Service 1.0 (RLS) FTF