Andrey Savchenko

This seems sound in spec, however WP's use of `@internal` is (as usual) inconsistent. On this, #37 and anything alike I am thinking towards standardizing behavior on default everything and...

I am all for better URLs, however in my opinion parser already butts in too much into site. Right now we cannot even keep it enabled on DevHub outside of...

Seems like this has been done in devhub reference. Anyone cares to comment on and/or document the process? It still doesn't seem like something Parser itself should do.

Thinking aloud — we already pull in like good chunk of PhpDocumentor, might make sense to just send the data with WP extras back to it.

I think the logical attempt would be to install PhpDocumentor and see what needs to happen to be able to plug WP Parser extras into it from that side.

So from this and some more discussion the current plan is to try implement "backstream" compatibility of sorts — try to achieve WP Parser providing its specific logic to phpDocumentor....

We can introduce for-convenience template tag in Parser. Like provide or configure printf template for source link and it will put the version and lines in. Just thinking aloud.

Had you seen specific use cases or just hypothetical? I would think deprecated code is still important to be in reference, it's omission could be very confusing.

I find limiting information about source counter-productive. You cannot _hide_ deprecated from people, they will encounter it anyway and need to be _educated_ about it. How do you expect someone...

I am afraid to look how that is, but I'll probably have to later. :)