Re: Surprising Precedence/Context

by Paladin (Vicar)

on Jun 02, 2017 at 18:03 UTC ( #1191995=note: print w/replies, xml )

Need Help??

As you can see below, the = binds tighter than the and, so your second example is parsing as:

(my($yes2)=defined $bad) and -f $bad;
[download]

Deparse:

[~]$ perl -MO=Deparse -e 'my($yes2) = defined $bad and -f $bad;'
-f $bad if my($yes2) = defined $bad;
-e syntax OK
[download]

Comment on Re: Surprising Precedence/Context Select or Download Code

Replies are listed 'Best First'.
Re^2: Surprising Precedence/Context by Anonymous Monk on Jun 02, 2017 at 18:46 UTC
When looking at precedence issues, the -p (full parens) Deparse option is helpful. `> perl -MO=Deparse,-p -e 'my($yes2) = defined $bad and -f $bad;' ((my($yes2) = defined($bad)) and (-f $bad));` [download]	[reply] [d/l]
Re^2: Surprising Precedence/Context by williams (Beadle) on Jun 02, 2017 at 19:04 UTC
Ouch. Thanks. Jim	[reply]

Domain Nodelet^?

Node Status^?

node history
Node Type: note [id://1191995]
help

Chatterbox^?

How do I use this? • Last hour • Other CB clients

Other Users^?

Others pondering the Monastery: (3)

As of 2023-12-10 17:58 GMT

Sections^?

Information^?

Find Nodes^?

Leftovers^?

Voting Booth^?

Notices^?