Re: %lookup

Here's one for the compiler writers:

Why do you persist in defining multiple variants of the same built-in function?

It was bad enough with 3 forms of trim but now 5 forms of lookup! Where will it end?

Trim should have been:
%TRIM( string {: option {: char}} )
where option is 'L', 'R', or 'B' with 'B' the default
and char is the character to trim with a space as the default

Lookup should have been:
%LOOKUP( needle : haystack {: option {: start {: limit }}} )
where option is 'EQ', 'LT', 'GE', 'GT', or 'LE' with 'EQ' the default
and the rest as they are.

I realise it's too late to correct this travesty but I wish you would stop perpetuating it.

Regards,
Simon Coulter.