KDM 1.4 RTF Avatar
  1. OMG Issue

KDM14 — VirtualCall is missing an Addresses

Open Closed All
  • Key: KDM14-79
  • Legacy Issue Number: 18779
  • Status: closed  
  • Source: Benchmark Consulting ( Stephane Vaucher [X] (Inactive))
  • Summary:

    Virtual calls should have an Addresses to indicate what is the object that is being passed a message. Currently, the only action relations that are required describe the parameters and the next control flow.

    IMO, a VirtualCall should match a PtrCall that requires a "Addresses relationship to the
    DataElement that represents
    the pointer". In the case of the Virtual call, it should probably read "Addresses relationship to the
    DataElement that represents
    the object", and perhaps specify that the DataElement should be of ClassUnit type.
  • Reported: KDM 1.3 — Fri, 14 Jun 2013 04:00 GMT
  • Disposition: Resolved — KDM 1.4
  • Disposition Summary:

    Change constraint for VirtualCall

    VirtualCall should use Addresses to the instance. However, the DataElement is of type DataElement, not ClassUnit, which is a subclass of Datatype
  • Updated: Tue, 12 Jul 2016 14:44 GMT