This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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.
Colons are not the problem: let the developers be free to choose what they prefer.
Colons are not the problem: let the developers be free to choose what they prefer.
IBM does not intend to provide a solution to this request at this time, so it is being closed.
For languages such as C and Java, style guidelines often recommend against defining multiple variables in the same definition. For example, http://www.informit.com/articles/article.aspx?p=2133373&seqNum=2.
As an aside, as suggested by Matt's comment, the syntax for this would require colons to separate the names being defined::
Dcl-s a : b : c int(10);
I'm not a fan of this at all. I think it will become harder to read and you could easily confuse variables.
Plus, with the example provided you could easily cut and past the data definition section and just paste after you define the variable name.
Jason
Nice idea - but it does make me nervous. I can envisage problems as this could so easily be misread:
Dcl LastCustomer Name Char(50); // Two separate variables declared
Dcl LastCustomerName Char(50); // One variable declared
Dcl LastCustomer_Name Char(50); // One variable declared
Dcl LastCustomer:Name Char(50); // Might be better - two separate variables declared
Hmmm - on balance I think it safest to declare each variable separately; clear and easy to maintain with no opportunity for misinterpretation
Don't other languages require a token separator when declaring variables? This example confuses keyword tokens from variable tokens.