in reply to Perl precedence details

I need 100% sure explanation ... without digging all the perldocs

That's going to be a problem, IIRC the knowledge on Perl's precedence is split up in a couple of places, the first that come to mind are of course perlop, the beginning of perlfunc, Prototypes in perlsub, with additional explanations in the Camel. Also you can fetch the prototypes of builtins via prototype, although AFAIK not all built-ins have prototypes because they are treated specially by Perl's parser.

a clear and unambiguous explanation (or algorythm)

Have you read On Parsing Perl, Perl Cannot Be Parsed: A Formal Proof, and the beginning of the PPI documentation? The following is pieced together from those links, also try running it through perl -MO=Deparse several times:

BEGIN { eval(time % 2 ? 'sub zany () {}' : 'sub zany {}') } # how to parse the following? does it die or not? zany / 1 ; # / ; die ;

Perhaps you could explain what you are trying to accomplish with this information?

Replies are listed 'Best First'.
Re^2: Perl precedence details
by hurricup (Pilgrim) on Jun 20, 2015 at 13:42 UTC

    Yes, i read all the links above and I know about perl ticks. But it's not what i need.

    I'm working on Perl5 IDEA plugin and currently re-working parser. Need to parse expressions properly in obvious situations. Without eval/regexp tricks or something.

    So i need to know how perl distincts named unary from rightward list calls in obvious situations. And which of built-ins treated as named unary operators.

      This thread already references plenty of good information on the topic, to the point where I'm not sure you're going to find much more, and including PPI, which already does a relatively good job of parsing Perl. It's unclear to me how all this information does or does not fit your needs. Can you perhaps give specific examples of code you or your parser find difficult to parse; maybe that will make explanation easier?

        Plenty of good information, but no specific answer to specific question.