Hi Andy > My feeling is that fluent builder is for authors/coders, not for >> machine/automatons. >> This is why I do like have things decomposed and human readable. You know >> what? >> > > My motivation is to use for automations and machines as well :-) > > thanks, Sergey > > > >> Building FIQL parser I was thinking that it would be good idea to have >> also >> user-friendly FIQL grammar with second set of tokens (e.g. with "=",">"... >> for "=eq=","=gt=" and so on). It is still quite easy to do so we can make >> up >> the full-blown parser that can consume: >> "name=foo* and (name!=*bar or level>10)" >> same way as FiqlParser consumes today this: >> "name==foo*;(name!=*bar,level=gt=10)" >> >> I've missed this one. This is exactly what I'd like the builder help users with, avoid typing raw FIQL queries :-). The builder should help producing "name=foo* and (name!=*bar or level>10)". Thus we will let users to type a search-language portable code because another builder instance will produce an XQuery/XPath expression, using the same sequence of builder calls
Hope you can see now my motivation thanks. Sergey (ok, whitespaces are not supported now, so it is an obstackle not to do this >> during cofee break :) >> >> cheers, >> -andy. >> >> >
