Pieter, I maintain our in-house logical construct macros, and ours does have ITERATEIF (AND LEAVEIF). However, using the "combo" operations (e.g. CLIJE) is problematical. The macros do not presently care what instructions generate the condition code, nor do they allow for specifying the conditional branch instructions. One of those facts would have to change. I haven't pursued it, as the generated code goes to a wide variety of customers, some of whom don't have the necessary hardware.
sas On Mon, May 15, 2017 at 7:46 AM, Pieter Wiid <pw...@mweb.co.za> wrote: > On 15/05/2017 13:42, Robin Vowels wrote: > >> From: "Pieter Wiid" <pw...@mweb.co.za> >> Sent: Monday, May 15, 2017 6:36 PM >> >> Branch to iterate is what I would LIKE. >>> >> >> You could try a BCT, or BXLE etc instruction. >> >> There is not such structure as the moment. If nobody else wants to play >>> with it, I will try to work on it when done with my current upgrade cycle. >>> >> >> --- >> This email has been checked for viruses by Avast antivirus software. >> https://www.avast.com/antivirus >> > > Again, I would like to see an ITERATE_IF, similar to the DOEXIT. > > Thus, I would have ITERATE_IF <cond>, instead of > > IF <cond> > > ITERATE > > ENDIF > > > The BXLE / BCT / JCT / JXLE are all catered for by the DO FROM constructs. > -- sas
