&& and and (well, you try searching for an answer)

[Melly]

Can someone explain the difference between && and and and or and ||?

Extra points if you can offer a search term for this on google and/or perlmonks that would help answer this without a new post.

Super bonus-points if you can render the first paragraph in acceptable and comprehensible english.

[explorer]

The difference is the precedence.

From perlop:

As more readable alternatives to "&&" and "||" when used for control flow, Perl provides "and" and "or" operators (see below). The short-circuit behavior is identical. The precedence of "and" and "or" is much lower, however, so that you can safely use them after a list operator without the need for parentheses:

[traveler]

Can someone explain the difference between && and and and or and ||?

'and' and 'or' are lower precedence

Extra points if you can offer a search term for this on google and/or perlmonks that would help answer this without a new post.

google for "perl logical operators"

Super bonus-points if you can render the first paragraph in acceptable and comprehensible english.

Can someone explain the difference between '&&' and 'and' and 'or' and '||'?

[apotheon]

refactor:

"Someone please explain the difference between '&&' and 'and', and the difference between 'or' and '||'."

[gellyfish]

and and or were introduced as lower precedence versions of && and ||, infact their precedence is guaranteed to be lower than any other operator so you can use them in places where otherwise you would have to use additional or otherwise unnecessary parentheses to ensure the correct meaning of a statement. This is probably clearest seen in:

open HANDLE, $file || die $!;

which is almost certainly a mistake (i.e. it won't die unless $file has a false value because the || has higher precedence than the comma in the argument list.) If you want to use || you would need to use the parentheses thus:

open(HANDLE, $file) || die $!;

Whereas:

open HANDLE, $file or die $!;

works fine.

In most places it is mostly a stylistic choice of whether to use the higher priority operator and more parentheses or not.

/J\

[GrandFather]

The && and || operators come from C and have the same relative precedence as they do in C. The and && or operators have been added to Perl with much lower precedence, even lower than assignment for example, which allows them to be used as statement joiners of using the Perl die idiom for example:

open ... or die ...;

The documentation for the operators can be found in the perlop man page. Note the precedence table at the start in particular.

[davidrw]

related thread: "or die" versus "|| die"

which points at a related Tutorial (see the "Precedence" section towards the bottom: Perl Idioms Explained - && and || "Short Circuit" operators

[shmem]

Since all has been explained, I'll head for the super bonus points... :-D

Can someone explain in which way the operator "and" differs from "&&", and "or" differs from "||"?

--shmem

[ysth]

Where are the pedants who would have you put your , inside the "? Thanks for not doing so.

[and]

&& and || should be used inside logical expressions while or should be used between statements for idiomatic error handling ("or die"). Finally, and is only useful for error handling with system.

[Melly]

Tnx all - the link to the earlier thread was particularily helpful.

[codeacrobat]

Apart from precedence issues && takes two chars and "and" three ;-)

P.S.

$_=$you_are; /just.*hacker/|/.*another $^X.*/ or $0=~/.pl$/ || die "no
+t a hacker"