Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Feb 16, 2021

Rhapsody 8.3.1 code generation with MISRAC++ limitations

Hi Team,

We have a problem,

1. The problem
We are using Rhapsody 8.3.1 with MISRAC++ profile.

For events the following code is generated:
ev_Bezel_KeyOk::ev_Bezel_KeyOk(const bool p_KeyOk) : OMEvent() ,KeyOk(p_KeyOk) {
setId(ev_Bezel_KeyOk_BezelPckg_DMsPckg_id);
}


which result in the following coverity (static code analyzer) warning:
"Bad call to a virtual method (VCALL_IN_CTOR_DTOR) call_to_virtual_method: Call to the virtual method setId"

setId() is a virtual method and virtualization doesn't work in the constructor. The base class method is invoked which is ok.
Technically there is no issue but we have to deal somehow with these coverity warnings - and the general policy it to fix rather than justify these.

Some possible solutions are
A) Calling the base class method:
ev_Bezel_KeyOk::ev_Bezel_KeyOk(const bool p_KeyOk) : OMEvent() ,KeyOk(p_KeyOk) {
OMEvent::setId(ev_Bezel_KeyOk_BezelPckg_DMsPckg_id);
}

B) Setting the lId member directly in the constructor:
ev_Bezel_KeyOk::ev_Bezel_KeyOk(const bool p_KeyOk) : OMEvent() ,KeyOk(p_KeyOk) {
lId=(ev_Bezel_KeyOk_BezelPckg_DMsPckg_id);
}

Idea priority Medium
  • Guest
    Reply
    |
    Mar 5, 2021

    Code generation is going thru many upgrades. Thanks for pointing this out.

    Will add this to our roadmap.

    Thanks!