This portal is to open public enhancement requests against IBM Z Software 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
As the comment below ways, this might make the language more complicated than needed. However, if an RFE were opened to allow '' to be assigned to AREAs, ENTRYs, and OFFSETs (as it is allowed today to be assigned to POINTERs and HANDLEs, this might be very useful in allowing more structures to be initialized via = ''
The "do ' ' once, copy the memory to a buffer and use the buffer to re-init" sounds a bit antiquated to me, i know that we had this in our coding guidelines once.
I'm not aware that the ''-init is a major performance problem for us, but this might differ from system to system.
Nowadays we try to use DEFINE and the VALUE(:XX:) wherever possible which is imho the more elegant way.
In general i advocate to use the existing functionality before introducing something new as adding options sometimes make it harder to find the right solution ;-),
just my 0.02€, johann
How smart can we make this? Maybe `empty(my_struct)` sets CHAR members to '', numeric members to 0, BIT members to '0'B, etc. That would be very handy!