SPM bug

2010-12-03 Thread Fred van der Windt
The syntax for AND and OR operators in the Strcutured Programming Macros is differs slightly between the UNTIL= and WHILE= options of the DO macro and every other SPM macro that supports conditions. This is not only very confusing but I was just bitten by the fact that the DO macro may silently

Re: SPM bug

2010-12-03 Thread Binyamin Dissen
On Fri, 3 Dec 2010 11:23:48 +0100 Fred van der Windt fred.van.der.wi...@mail.ing.nl wrote: :The syntax for AND and OR operators in the Strcutured Programming Macros is differs slightly between the UNTIL= and WHILE= options of the DO macro and every other SPM macro that supports conditions. This

Re: SPM bug

2010-12-03 Thread Fred van der Windt
:But why is this error not properly signalled? Because it wasn't coded to do it. Anyway, I asked the 'right person in our organization' to report it to IBM as a bug in the HLASM Toolkit. Fred! - ATTENTION: The information in

Re: SPM bug

2010-12-03 Thread Fred van der Windt
Ouch! Otiose tokens should not be silently ignored. Would: DO UNTIL=((CR,R1,LT,R2),AND,(CR,R3,LT,R4)) .. have produced the intended result? Yes it does: DO UNTIL=((CR,R1,LT,R2),AND,(CR,R3,LT,R4)) +...@lb2 DC 0H : : ENDDO +...@lb3

Re: SPM bug

2010-12-03 Thread Fred van der Windt
Trouble comes when the SPMs are used by people who do not/cannot write macro definitions. Ah. So if I code a macro invocation with parameters that do not meet the documented specification of that macro, but the macro ignores the incorrect parameters and uses the remaining parameters to

Re: SPM bug

2010-12-03 Thread Paul Gilmartin
On 2010-12-03 14:45, Fred van der Windt wrote: Trouble comes when the SPMs are used by people who do not/cannot write macro definitions. Ah. So if I code a macro invocation with parameters that do not meet the documented specification of that macro, but the macro ignores the incorrect