- May 07, 2012
-
-
Adam Radziszewski authored
fix match token-level condition: immediately terminate and return empty match result when curr pos is outside sent
-
- Apr 30, 2012
-
-
Adam Radziszewski authored
-
- Feb 28, 2012
-
-
Adam Wardynski authored
-
- Dec 01, 2011
-
-
Adam Radziszewski authored
-
- Sep 26, 2011
-
-
Adam Radziszewski authored
-
- Sep 16, 2011
-
-
Adam Radziszewski authored
-
Adam Radziszewski authored
-
Adam Radziszewski authored
-
- Sep 15, 2011
-
-
Adam Radziszewski authored
-
- Sep 08, 2011
-
-
Adam Radziszewski authored
-
- Sep 07, 2011
-
-
Adam Radziszewski authored
-
- Aug 04, 2011
-
-
Adam Radziszewski authored
-
Adam Radziszewski authored
-
- Jun 28, 2011
-
-
ilor authored
-
- Jun 10, 2011
-
-
Bartosz Broda authored
-
- Jun 09, 2011
- May 09, 2011
-
-
Adam Wardynski authored
Allows for application of all rules on an annotated sequence via apply_all method.
-
- May 06, 2011
-
-
Adam Wardynski authored
It was returning Position based off absolute position, which was no good for operators like orth[first(M)] working in changing sentence contexts.
-
Adam Wardynski authored
This reflects the fact that positions stored in matches are absolute positions, while Position type is used in the language as position relative to current position in the sentence context. So mixing the two was confusing at the very least. This also actually fits the most recent version of spec, which no longer mentions Position, either.
-
- May 05, 2011
-
-
Adam Wardynski authored
-
Adam Wardynski authored
-
- Apr 29, 2011
-
-
Adam Wardynski authored
-
- Apr 28, 2011
-
-
Adam Wardynski authored
-
Adam Wardynski authored
-
Adam Wardynski authored
-
- Apr 27, 2011
-
-
ilor authored
-
- Apr 26, 2011
-
-
Adam Wardynski authored
-
ilor authored
-
Paweł Kędzia authored
longest() and oneof() operator takes boost::shared_ptr<std::vector<boost::shared_ptr<ConjConditions> > >
-
Adam Wardynski authored
-
Adam Wardynski authored
So it's clear it's not about MatchRule at all.
-
ilor authored
-
- Apr 22, 2011
-
-
Adam Wardynski authored
-
Adam Wardynski authored
1) MatchOperator was essentially a wrapper for "match" section of "apply" operator 2) Other operators like Repeat actually used ConjConditions directly, without using MatchOperator - so ApplyOperator could too! 3) The confusion was about "match" referring both to part that is matching sentence against match conditions, and the results of this matching process. That led e.g. to "match_operator" rule in grammar, which was unlike "strset_operator" rule and the like. "match_operator" was about the "match" section in "apply" and now it is more straightforward. Next step should rename "match_fit" to be actual "match_operator", consistent with "XXX_operator" for other XXX types.
-
- Apr 21, 2011
-
-
Adam Wardynski authored
-
Adam Wardynski authored
-
Adam Wardynski authored
-
ilor authored
-
Adam Wardynski authored
-