in reply to Annotations for Perl

I might be missing something and thereby not understanding your intent, but what's wrong with using why not use POD documentation?

Replies are listed 'Best First'.
Re^2: Annotations for Perl
by hurricup (Pilgrim) on Jun 02, 2015 at 16:38 UTC

    To use pod, i need to make strict rules, how to write it so IDE parser could interpret it. And those rules should not break the html compiled pod

    And pod is for human reading i belive, not machine.

      POD's =for might help there, e.g.

      =for ide @Returns Foo::Bar

      AFAIK POD parsers will ignore that if they don't recognize "ide", but your parser could pull those out.

        Interesting idea. But there is a one thing which is bad for this case - excessive new lines. As far as i remember, let's say pod statement should have \n\n as it's end. So our annotation should be like:

        =for ide @returns Foo::Bar =cut sub somefunc(){...}
        Isn't it too messy?