Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expression language: for_all hard to read and whitespace aware parser needed #2

Open
pieterbos opened this issue Jul 5, 2016 · 0 comments

Comments

@pieterbos
Copy link

consider the following expression snippet:

for_all $event in /data/events /some/other/path > $event/items/value

This is quite hard to read, plus the parser needs to be whitespace aware in order to understand wh. Xpath solved this in xpath 2 and 3 with the following syntax:

every $event in /data/events satisfies /some/other/path > $event/items/value

And

some $event in /data/events satisfies /some/other/path > $event/items/value

So, we can do:

  • use 'for_all ... in ... '. I'm not a native English speaker, but I cannot find anything that works well and is much shorter than 'for_all ... in ... the following must evaluate to true', compared to 'for_all ... in
  • use the 'every .. in ... satisfies'-syntax from xpath
  • make the parser whitespace aware

I would prefer the 'every'-syntax, but if someone has a good suggestion for what comes after for_all...

@pieterbos pieterbos changed the title expression language: for_all hard to read and whitespace aware parser needed Expression language: for_all hard to read and whitespace aware parser needed Jul 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant