#
23647573 |
| 21-May-2023 |
Nikita Popov |
Represent names using string rather than array of parts In most circumstances we are interested in the whole string, not the parts split by namespace separator. As names are common, this
Represent names using string rather than array of parts In most circumstances we are interested in the whole string, not the parts split by namespace separator. As names are common, this representation measurably improves memory usage and performance.
show more ...
|
#
032b1021 |
| 11-Sep-2022 |
Nikita Popov |
Remove deprecated Error constructor And use this chance to provide accurate position information for namespace errors.
|
#
03ccfa3d |
| 03-Sep-2022 |
Nikita Popov |
Rename Stmt\DeclareDeclare to DeclareItem
|
#
23835d20 |
| 03-Sep-2022 |
Nikita Popov |
Rename Scalar\LNumber to Scalar\Int_
|
Revision tags: v4.3.0, v4.2.5, v4.2.4, v4.2.3, v4.2.2, v4.2.1, v4.2.0, v4.1.1, v4.1.0, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v3.1.5, v4.0.0beta1, v3.1.4, v4.0.0alpha3, v3.1.3, v4.0.0alpha2, v3.1.2, v4.0.0alpha1, v3.1.1, v3.1.0, v3.0.6 |
|
#
a6846e3b |
| 28-Apr-2017 |
Nikita Popov |
Always use Identifier nodes The parser will now always generate Identifier nodes (for non-namespaced identifiers). This obsoletes the useIdentifierNodes parser option. Node
Always use Identifier nodes The parser will now always generate Identifier nodes (for non-namespaced identifiers). This obsoletes the useIdentifierNodes parser option. Node constructors still accepts strings and will implicitly create an Identifier wrapper. Identifier implement __toString(), so that outside of strict-mode many things continue to work without changes.
show more ...
|
Revision tags: v3.0.5, v3.0.4, v3.0.3 |
|
#
953f8c96 |
| 19-Jan-2017 |
Nikita Popov |
Perform automated test update
|
Revision tags: v3.0.2, v3.0.1, v3.0.0, v3.0.0beta2 |
|
#
caa5c0cc |
| 08-Oct-2016 |
Nikita Popov |
Graceful handling for "special" errors Nearly all special errors are now handled gracefully, i.e. the parser will be able to continue after encountering them. In some cases the assoc
Graceful handling for "special" errors Nearly all special errors are now handled gracefully, i.e. the parser will be able to continue after encountering them. In some cases the associated error range has been improved using the new end attribute stack. To achieve this the error handling code has been moved out of the node constructors and into special methods in the parser.
show more ...
|
Revision tags: v3.0.0beta1, v2.1.1, v3.0.0alpha1, v2.1.0, v2.0.1, v2.0.0, v2.0.0beta1, v1.4.1, v2.0.0alpha1, v1.4.0, v1.3.0 |
|
#
0731b476 |
| 30-Apr-2015 |
Nikita Popov |
Don't distinguish test-fail / test With error recovery this is fluid. Using .test for everything.
|