> That's some mighty fine left brain thinking there( especially for a Monday morning ), but does it in anyway affect any practical aspect of Perl?
The first comment.
The first comment.
"But that will not happen in practice"
If you think that to be the case, use a language that _can_ be parsed. That makes life easier for implementers of IDE's, refactoring tools, etc. and costs you nothing (given the "that will not happen in practice" claim)
Infact it says: "only Perl can parse Perl".
On the other hand JavaScript has esprima that is written in JavaScript, and also other languages like Python can parse themselfs.
As a Perl programmer, I don't know if it is a pro or a cons. For example Perl::Critic cannot parse some costructs, cause they are too complicated. What I usually do, as in many other contexts, I try to understand what is the subset of features I need to use.