Thanks. Some of those give the expected results with the "/" syntax.
For some background: I am in the process of figuring out and describing the different phases of parsing search queries.
Everything 1.5 has a lot more search possibilities and with that, serach queries can get longer and more complex.
Especially with nested preprocessor-/"column"-/search-functions.
Recently a lot of the search queries I produce can be measured in meters instead of words (figure of speech).
So knowing the details of the parsing could really help in troubleshooting those.
This was just "Step 1" in trying to figure this out. So I still really like to know *why* the A:=#[ .. syntax fails, even though I don't actually need it.
For some background: I am in the process of figuring out and describing the different phases of parsing search queries.
Everything 1.5 has a lot more search possibilities and with that, serach queries can get longer and more complex.
Especially with nested preprocessor-/"column"-/search-functions.
Recently a lot of the search queries I produce can be measured in meters instead of words (figure of speech).
So knowing the details of the parsing could really help in troubleshooting those.
This was just "Step 1" in trying to figure this out. So I still really like to know *why* the A:=#[ .. syntax fails, even though I don't actually need it.
Statistics: Posted by NotNull — Mon Dec 16, 2024 11:35 am