Mike O'Regan

Had to go to backpan to find PPI::Tinderbox, and the latest there is 0.08. Was that the last release (January 2005)?

Doesn't have to be a method call for 'x' to get parsed as a word: ``` ppidump 'my $line = join(LD_X, map{LD_H x ($_+2)} @$widths);' PPI::Document PPI::Statement::Variable [ 1, 1,...

not limited to the 'x' operator. see 'cmp' below: ``` ppidump 'sort { $a->package cmp $b->package } ();' PPI::Document PPI::Statement [ 1, 1, 1 ] PPI::Token::Word 'sort' PPI::Structure::Block { ......

The `my $line = join(LD_X, map{LD_H x ($_+2)} @$widths);` case above simplifies down to `bareword x 1`

Is there anything special to using the term "namespace" as opposed to "package"? I can imagine having both $node->package (for a PPI::Statement::Package) and $node->package_name (for a string).

The issue of what to do after a statement-that-is-really-an-expression ends with more to parse seem similar to https://rt.cpan.org/Ticket/Display.html?id=36555

Confirmed in PPI 1.220 and on my development branches. ``` ppidump '"a".1' PPI::Document PPI::Statement [ 1, 1, 1 ] PPI::Token::Quote::Double '"a"' [ 1, 4, 4 ] PPI::Token::Number::Float '.1' ``` Thank...

Request for comments: are there more operators that dictate that what follows them must be a hash constructor and not a block? %PPI::Lexer::CURLY_CLASSES contains, among other things, operators that cannot...

Currently PPI disambiguates hashes and blocks by checking for a few cases where a hash interpretation of {} compiles and a block interpretation does not: 'scalar', '||=', ',', '=', '=>'....

If this will help you and we'll get more releases out, I'm willing to go with it. (I would like master to (continue to) always pass all tests.) I see...