Re: Macro Behavior

2018-10-23 Thread Peter Relson
If you look at just about all recent macros, they have far more checking than that. And that's good. Checking simply for "" does not work for ESPIE because it has acceptable positional parameters which vary according to the rest of the specification. And in fact the OP's example would not have

Re: Macro Behavior

2018-10-22 Thread Rob van der Heij
On Fri, 19 Oct 2018 at 19:04, Peter Relson wrote: > There is no "should" in this sort of situation. There is a "could". There > is a "wouldn't it be nice if". > > Could it be done? Sure. Would having done so have helped this case? Sure. > Would doing so be a better use of limited resources than

Re: Macro Behavior

2018-10-19 Thread Tony Harminc
On 18 October 2018 at 11:34, Jonathan Scott wrote: > I check for ('(n)' EQ '') where n is one more than the valid > number of positional parameters. I do this rather than checking > N' so that it will tolerate a trailing comma, for example when > a macro has one positional parameter which is

Re: Macro Behavior

2018-10-19 Thread Steve Thompson
Thank you. You answered my real question. And so with that knowledge I can say that the RFE is like screaming in space. No one will hear. Sent from my iPhone — small keyboarf, fat fungrs, stupd spell manglr. Expct mistaks > On Oct 19, 2018, at 1:03 PM, Peter Relson wrote: > > There is no

Re: Macro Behavior

2018-10-19 Thread Peter Relson
There is no "should" in this sort of situation. There is a "could". There is a "wouldn't it be nice if". Could it be done? Sure. Would having done so have helped this case? Sure. Would doing so be a better use of limited resources than doing something else? There is no requirement that a

Re: Macro Behavior

2018-10-18 Thread Steve Thompson
hursday, October 18, 2018 3:27 PM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: Re: Macro Behavior > > I think in this case, ESPIE, it should check for extraneous operands. It > evidently has a maximum of 3 positional operands, and it would certainly > complain if MF(E(1)) was one of

Re: Macro Behavior

2018-10-18 Thread Charles Mills
+1 Charles -Original Message- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Steve Smith Sent: Thursday, October 18, 2018 3:27 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Macro Behavior I think in this case, ESPIE, it should check

Re: Macro Behavior

2018-10-18 Thread Steve Smith
I think in this case, ESPIE, it should check for extraneous operands. It evidently has a maximum of 3 positional operands, and it would certainly complain if MF(E(1)) was one of them. Re allowing a trailing comma: I wouldn't, and I think Jonathan's justification is off the mark. The check for

Re: Macro Behavior

2018-10-18 Thread Jonathan Scott
Ref: Your note of Thu, 18 Oct 2018 11:30:09 -0400 Steve Thompson writes: > I have a question. If one passes too many positional arguments to > a macro, should one not issue an MNOTE about this? > > Please try the following, and let me know what you think about this: > > ESPIE

Macro Behavior

2018-10-18 Thread Steve Thompson
I have a question. If one passes too many positional arguments to a macro, should one not issue an MNOTE about this? Please try the following, and let me know what you think about this: ESPIE SET,MYRTN,(1,3,7),PARAM=(3),MF(E,(1)) --- Yes, the above should have "="