That’s why I gave my initial reaction. I looked at the documentation and according to the diagram it looks like the keyword parameters should be before the input range. I didn't see any remark that keywords can be used anywhere in the command, though it also doesn't specifically state they are in fixed order.
According to the documentation there are three groups of arguments. First the keywords, next the input range and third output keywords (DETAIL, MASTER). Looking further down, there are a few examples. One of them states: /* Now find uniques */ 'callpipe (end ?) *: | l:lookup 1.5 autoadd keyonly ? l: | *:' So this example suggests you can place keywords like autoadd or keyonly also after the input range. And apparently it works, as long as there are 2 input ranges specified or the keyword after 1 input range doesn't start with an abbreviation of an input selector (such as W of F). Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven -----Original Message----- From: CMSTSO Pipelines Discussion List <[email protected]> On Behalf Of Rob van der Heij Sent: Friday, 29 January 2021 13:43 To: [email protected] Subject: Re: [CMS-PIPELINES] Lookup with floor Caution! External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe. On Fri, 29 Jan 2021 at 12:48, John P. Hartmann <[email protected]> wrote: > There is something wrong here. LOOR is not a valid range, so F should > not be recognised as a abbreviation of FIELD, but it certainly looks > like that is what is happening. > It sure has bitten me before that LOOKUP was picky on the order of arguments, but never gave it much thought. I'm surprised that we accept the options after the input ranges, since the syntax diagram clearly doesn't. There's room for improvement. Rob This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos’ liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.
