- May 06, 2011
-
-
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.
-
Adam Radziszewski authored
-
- May 05, 2011
-
-
Adam Wardynski authored
-
Adam Wardynski authored
-
Adam Wardynski authored
-
Adam Wardynski authored
-
Adam Wardynski authored
-
Paweł Kędzia authored
-
Paweł Kędzia authored
-
Adam Radziszewski authored
-
Adam Radziszewski authored
-
Adam Radziszewski authored
-
ilor authored
-
ilor authored
-
Adam Wardynski authored
-
ilor authored
-
ilor authored
-
ilor authored
-
Adam Radziszewski authored
-
- May 04, 2011
-
-
Adam Wardynski authored
It didn't like passing reference to something that could be treated as a value.
-
Adam Wardynski authored
Variables is noncopyable but default copy constructor was apparently working in VS.
-
Adam Wardynski authored
-
Adam Radziszewski authored
-
Adam Radziszewski authored
-
Adam Radziszewski authored
-
Adam Wardynski authored
-
Adam Wardynski authored
Each subsequent rule was reusing variables object, which wasn't good. Parsing of sequences had to be changed not to end with semi, and it wasn't actually passing on lexicons in the first place.
-
Adam Radziszewski authored
-
Paweł Kędzia authored
-
Paweł Kędzia authored
-
Paweł Kędzia authored
-
Paweł Kędzia authored
-
Paweł Kędzia authored
-
Paweł Kędzia authored
-
Paweł Kędzia authored
-
Paweł Kędzia authored
-
Paweł Kędzia authored
-
Paweł Kędzia authored
-
Paweł Kędzia authored
-
Paweł Kędzia authored
-