Jantje wrote: >Commas at the beginning or at the end makes no difference... :
As far as the language syntax goes, this is a true statement. As far as maintainability goes, that is another story. When I continue a statement, I prefer to break between arguments, as there is typically less of language semantic connection between arguments than within argument. Assuming we're not talking about quoted commas, which are entirely different animals, I respectfully disagree for these reasons: 1. Two commas at the end of a line are clearly the end of an argument within a continued statement. A single comma at the end of a line is a simple continuation. 2. Putting the argument delimiting comma at the beginning of a line means that you have to remember to look at the beginning of the next line. That's easy to forget/miss if you are skimming. 3. If you rearrange a statement, you can replace a line without a leading comma with one that has such, and vice versa, with avoidable and/or disastrous results. 4. To the best of my knowledge, most experienced REXX programmer's put an argument delimiting comma at the end of the line (followed by the continuation comma). The more code you write (in a language) the more you recognize which subtle things are more error prone and which are less so, in that language. Just my 2 cents. OREXXMan JCL is the buggy whip of 21st century computing. We want Pipelines in the z/OS base. On Mon, Apr 9, 2018 at 9:37 AM, Phil Smith III <li...@akphs.com> wrote: > Jantje wrote: > > >Commas at the beginning or at the end makes no difference... : > > > > Right, nobody thought it would. That was a style point. > > > > If your function call is still failing as you indicate: > > > > > 87 +++ > >RS=ALERTSN(SEV,TYPENAME,ELEMENT,DESC,STATUS,STSDESC,, > SUBSRC,SOURCE,LOCATION > ,SYSTYPE,PLTFTYPE,IMPACT,HOST,,MONENV,RESOURC > > >E,EXTRINFO,ACTIVE,CLOSING,FTPERR,,APPLTYPE,APPLNAME,UNIQUE) > > >IRX0040I Error running ALERTSNB, line 87: Incorrect call to routine > > > > Then you're apparently calling it wrong. I see double commas in the error > output: that suggests you have doubled commas in the wrong place, because > if > they're seen as continuation, ALERTSN won't see them at all. > > > > Run it with TRACE I and see what it's getting. > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
