That does sound like a conflict. Do you think we should make a reserved word list and have the function factory registry reject functions that cannot be used? However...
The function does have some use as a filter, to process a parameter for example. On Tue, Apr 30, 2019 at 2:25 AM Niels Charlier <ni...@scitus.be> wrote: > Hello, > > I discovered that the implemented and documented filter function "not" > doesn't actually work. > > The parser treats the word "not" as a reserved word, used for filters, > therefore it does not manage to parse it as an identifier inside an > expression. > > Perhaps I am missing something, but otherwise the function should > probably be renamed or removed? > > I'm not sure if there is much other use for it: > - there is a notEqualsTo, and I don't know if there are any other > boolean functions besides equality tests > - there is no function for "and" and "or", so complicated boolean > expressions are not possible > - boolean expressions are probably only used as condition for > if_then_else, and you can always switch the then and the else > > Regards > > Niels > > > > _______________________________________________ > GeoTools-Devel mailing list > GeoTools-Devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel > -- -- Jody Garnett
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
