/me bows and thanks the academy.
Sounding board eh?
The only problem with _that_ is that PPI is so frigging finicky that it
can be difficult to explain the context of the problems for the
decisions regarding the internals. :)
Of course, if anyone is interested in helping, there are about a zillion
unit tests that need to be written...
*crickets*
In all seriousness, part of the job will be moving everything into
SourceForge once I get 0.840 out the door. So if anyone wants to talk
about PPI or help out in any way, or start one of the 50 or so modules
that we can build on top of it, my doors are open to volunteers.
Todays issue:
- Making Element->location "Just Work" while taking into account
here-docs, and selectively caching so that it isn't a dog.
Upcoming issues:
- Detecting the use of source filtering modules, and knowing which ones
modify the grammar far enough to break the lexer (and thus we should
refuse to parse the file) and which ones we can tolerate.
- Normalising PPI::Token::Quote objects for the four quote types ('',
"", q, qq) into a single value for use in PPI::Compare.
(Coming up with a generic solution (just in written terms) would be
something that should be fairly approachable without knowing the internals)
- Making the Lexer/Tokenizer capable of "reflowing", so that you can
insert arbitrary text at some point in the PDOM tree and the document
will morph to take it into account.
(Yes, I'm aware that last one is going to chew a shitload of CPU) :)
Adam
Stevan Little wrote:
Congratulations to our illustrious list member Adam on getting Perl
Foundation Funding for PPI.
(http://search.cpan.org/src/ADAMK/PPI-0.840_01/Changes)
Adam, please feel free to use the list as a sounding board if you like,
I for one have great hopes for this module.
- Steve
_______________________________________________
sw-design mailing list
sw-design@xxxxxxxxxxxx
http://metaperl.com/cgi-bin/mailman/listinfo/sw-design
|
