This is an IBM Automation portal for Cloud Platform products. 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Operation arguments in RSA-RTE C++ have a direction that is presented at several levels. For converted RoseRT elements the direction appears to default to "In Out". Most of the time this is wrong. Is it possible to leave this as unspecified during conversion instead of choosing a default that is often wrong? Maybe the fixup plugin can assist.
Feature request: When adding arguments to an operation, the direction defaults to "In". Can this be made language specific and dependent on the type? So for C / C++: pass-by-value == "In" pass-by-pointer == "In Out" pass-by-reference == "In Out" pass-by-const-pointer == "In" pass-by-const-reference == "In" Note that these are the defaults and might still be not 100% correct. But they will be correct most of the time.
Alternative: Add possibility to hide the direction from all views. If it has no effect on code generation and is often wrong, then do not show it. Question: What is the direction used for? Is there a relation with doxygen?
Do not place IBM confidential, company confidential, or personal information into any field.