DDS 1.0 NO IDEA Avatar
  1. OMG Issue

DDS — Naming_of_attribute_getter_operations

  • Key: DDS-52
  • Legacy Issue Number: 6758
  • Status: closed  
  • Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)
  • Summary:

    Naming_of_attribute_getter_operations

    DataWriter class table, and DataReader class table operations
    get_liveliness_lost_status, get_offered_deadline_missed_status and
    get_offered_incompatible_qos_status.

    In the IDL file, these getter methods are specified as readonly
    attributes with the same names, but without the preceeding
    "get_". This leads to getter methods with different names in different
    languages (In C++ the"get_" part will disappear, in Java only the "_"
    will disappear).

    These IDL-to-language mappings would invalidate the PIM. To avoid
    this kinds of issues we should avoid using attributes in either the
    PIM or the PSM. The use of explicit operations will make the PIM more
    easily mappede to different PSMs.

    **PROPOSAL**

    Replace the readonly attributes in the PIM or PSM with explicit
    get_xxx operations. Replace any read-write attributes attributes in
    the PIM or PSM with explicit get_xxx and set_xxx operations.

  • Reported: DDS 1.0b1 — Tue, 23 Dec 2003 05:00 GMT
  • Disposition: Resolved — DDS 1.0
  • Disposition Summary:

    see below

  • Updated: Fri, 6 Mar 2015 20:58 GMT