HAL4RT 1.0 FTF Avatar
  1. OMG Issue

HAL4RT — Inconsistent definition of notify_event(), and return value of "notify_event" seems not necessary

  • Key: HAL4RT-6
  • Status: open  
  • Source: AIST ( Dr. Noriaki Ando)
  • Summary:

    The definition of notify_event() functions in "ApplicationBase" and "Event" are inconsistent.

    p.19, 7.4.3, Figure 7.6
    ApplicationBase::notify_event() is defined as having int type return value.

    p.20, 7.4.3.1, Table 7.6
    notify_event()'s return type is not defined explicitly, but definition of class and interface table in 7.2 describes as follows: "Also, as the type of return code for every operation in this specification is Returncode, which is defined in Section7.3, Return Codes, this is omitted in the description table."
    Therefore, return type of the notify_event() is ReturnCode from the definition in the table.

    p.21, 7.4.3.2, Table 7.7
    Return type of the notify_event() is ReturnCode from the definition in the table.

    p.23, 7.4.5, Figure 7.8
    Event::notify_event() is defined as no retunr value.

    p.33, 7.5.2 C PSM
    ApplicationBase::notify_event(), Event::notify_event() are defined as habing int32_t type return value.

    Since the notify_event() functions are just callback functions, return value of "notify_event" seems not necessary.

  • Reported: HAL4RT 1.0b1 — Mon, 14 Mar 2016 17:36 GMT
  • Updated: Mon, 6 Nov 2017 12:34 GMT