PHP-Parser/test/code/parser/nopPositions.test

Positions for leading nop statement
-----
<?php
/* Comment */
-----
!!positions
array(
    0: Stmt_Nop[2:14 - 2:13](
        comments: array(
            0: /* Comment */
        )
    )
)
-----
<?php
{
    /* comment */
}
-----
!!positions
array(
    0: Stmt_Nop[3:0 - 3:17](
        comments: array(
            0: /* comment */
        )
    )
)
Fix attributes for zero-length nop nodes Previously zero-length nop nodes used the lookahead start attributes and current end attributes. This choice ends up being somewhat weird, because the end attributes will be the at the last non-whitespace, non-comment token, which might be quite far back. More problematically, we may not have encountered any non-discarded token if we're at the start of the file, in which case we will have no end attributes to assign. Change things to use a canonical "zero-length" node representation, where the end position (token & file) will be exactly one before the start position. Fixes #589. 2019-05-11 20:01:25 +02:00			`Positions for leading nop statement`
			`-----`
			`<?php`
			`/* Comment */`
			`-----`
			`!!positions`
			`array(`
			`0: Stmt_Nop[2:14 - 2:13](`
			`comments: array(`
			`0: /* Comment */`
			`)`
			`)`
Place Nop nodes more precisely If the Nop is created to collect comments, place it directly after the comment, instead of at the next non-whitespace character. 2020-02-09 17:10:33 +01:00			`)`
			`-----`
			`<?php`
			`{`
			`/* comment */`
			`}`
			`-----`
			`!!positions`
			`array(`
			`0: Stmt_Nop[3:0 - 3:17](`
			`comments: array(`
			`0: /* comment */`
			`)`
			`)`
Fix attributes for zero-length nop nodes Previously zero-length nop nodes used the lookahead start attributes and current end attributes. This choice ends up being somewhat weird, because the end attributes will be the at the last non-whitespace, non-comment token, which might be quite far back. More problematically, we may not have encountered any non-discarded token if we're at the start of the file, in which case we will have no end attributes to assign. Change things to use a canonical "zero-length" node representation, where the end position (token & file) will be exactly one before the start position. Fixes #589. 2019-05-11 20:01:25 +02:00			`)`