RLS 1.1 NO IDEA Avatar
  1. OMG Issue

RLS11 — Type of InterfaceBase::get/setParameterValues() argument in C++ PSM

  • Key: RLS11-36
  • Legacy Issue Number: 16207
  • Status: closed  
  • Source: ETRI ( Jaeyeong Lee)
  • Summary:

    Argument type of InterfaceBase::get/setParameterValues is 'set' in PIM but 'list' in PSM. It may cause the developers confusing.

  • Reported: RLS 1.0 — Sun, 8 May 2011 04:00 GMT
  • Disposition: Resolved — RLS 1.1
  • Disposition Summary:

    In C++ PSM, we found several points of similar inconsistency:

    • std::vector is used to denote ordered list in some definitions and std::list is used
      for other definitions
    • ordered and non-ordered list sometimes does not match the definition in PIM
      In order to clearly represent the PIM, the following rule will be applied for PIM =
      C++ PSM mapping:
    • non-ordered list will be mapped to std::set
    • ordered list will be mapped to std::vector
      Based on these rules, the followings points will be modified in C++ PSM:
    • Modify InterfaceBase::getParameterValues() and setParameterValues()
      methods to use std::set
    • Modify SetParameter class to bind to::std::set<T> for template parameter
    • Modify SetParameter.attrs attribute to use std::vector
    • Modify ServiceAbility.inStreamAbilities attribute to use std::set
    • Modify Service.getChild () method to use std::vector
    • Modify Service.inStreams and outStreams attributes to use std::vector
      In addition, we found that there are some inconsistency between the table
      description and UML, and these will be fixed as following:
    • In Service class, based on the text description, the attributes inStreams and
      outStreams will be marked as “N ord” in the table and will be marked as
      “ordered” in the UML diagram
  • Updated: Fri, 6 Mar 2015 20:58 GMT