Damian Conway wrote:
> You gave the hint that comments are also in the parse tree.
They can be. Better still, the (raw) Pod can also be kept in the parse
tree...since, like comments, the Perl parser still has to recognize it, even
when it's focusing on extracting Perl.
...And since the Perl parser is required to include the Pod Parser (I
think), what gets included in the Perl parse tree for a Pod Section
will very likely be much more structured than what would get included
for a comment: the former will actually _have_ structure (and meaning)
which can be made available to introspection, while the latter will
continue to be merely an undifferentiated lump of text.
For example, I would expect semantic Pod Sections that appear within
class Foo's definition to be accessible via Foo.WHY, much like the
implementation details themselves show up in Foo.HOW.
> So, that is sufficient for me:
And for others too, I hope.
Defining Perl 6 and Pod 6 independently opens up so many options for
building documentation tools:
What sold me on it was Larry's suggestion that they only need to be
thought of separately from Pod's perspective. From Perl's
perspective, Pod can be thought of as part of the Perl language.
--
Jonathan "Dataweaver" Lang
