In general, pipes are forgiving and accepts a wider gamut of options
than the documentation specifies.
The documentation is written to be comprehensible and flowing (in
authors' argot), if it were to show all possible combinations of options
and what not, it would, certainly in the case of lookup, be
incomprehensible.
In this particular case, "exclusive" means that the last one wins. But
admittedly, sometimes it does mean what it says.
Changing existing code to follow the book, particularly when the code
has been in the field for twenty years, is not considered a good idea,
in some quarters, at least.
If you insist on IBM fixing this, two things will happen:
1. It will come back to bite you, particularly where you think it is
unrelated. I consider that well deserved.
2. If sufficiently insistent, you will force a fix that will break code
for the silent majority. And then all hell breaks loose.
In the current setup, I doubt any of this will happen, but it has in the
past.
Let me illustrate this with a story from real life:
Back before your grandma was born, telephone systems used what was
called "in-band signalling". In particular, a pure 3000 Hz tone would
signal that a party had hung up and the call would be dismantled.
Now, apart from "phone phreaks", it so happened that a lady somewhere in
the south west of this island had a set of dentures that gave off this
exact note. She complained vigorously to the phone company, and while
she was technically in the right that they had a design error (as had
every phone system in the world at that time), the problem was resoled
by the phone company buying her a different set of dentures.
On 1/29/21 18:52, Alain Benvéniste wrote:
I also tried a "lookup autoadd ceiling floor 1-* master".
Point 13 in the doc says these options are mutually exclusive, but pipe doesn't
reject it.
Case opened.
