IBM Support

PI11151: StandardOperations property overrides visibility of other class members

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Permanent restriction.

Error description

  • StandardOperations property set to some overridden operators.
    
    In most cases this functions correctly. The class members
    immediately following the above code are correctly placed in the
    visibility specified in their own settings. For example:
    
    //#[ ignore
            private:
             //some overridden operators
    //#]
    
    ////    Constructors and destructors    ////
    
        public :
    
            some_operation()
    
    However, in one class, the class members directly following the
    StandardOperation's Declaration property, the operations are
    having their visibility affected by the preceding code. For
    example:
    
        //#[ ignore
            private:
             //some overridden operators
    
    
           // types with vis set to public
        //#]
    
    Notes:
    ====
    
    - Could only reproduce this issue with customers model.
    
    Workaround:
    ========
    They add an extra line to the existing StandardOperation's
    Declaration property. For example:
    
    private:
     // some overridden operators
    public: //workaround
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    User is not suppose to change the access of standard
    operations. If he does - he will change the access of
    following code.
    He can avoid that - by adding a public access after the
    operations - as this user did.
    The reason this happens only for this class is that it has a
    source artifact - meaning that the user is responsible for
    the order of elements inside the class - so the operations
    are being added above all other code.
    So a simple to avoid even that is to delete the source
    artifact
    

Problem conclusion

  • This is how the feature is designed to work.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI11151

  • Reported component name

    TLOGIC RHAPSODY

  • Reported component ID

    5724V74RP

  • Reported release

    805

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-06

  • Closed date

    2014-05-21

  • Last modified date

    2014-05-21

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7P9W","label":"Rational Rhapsody"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.5","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
21 May 2014