File: precedence.rdoc

package info (click to toggle)
ruby3.4 3.4.5-1~exp1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 154,784 kB
  • sloc: ruby: 1,259,653; ansic: 829,955; yacc: 28,233; pascal: 7,359; sh: 3,864; python: 1,799; cpp: 1,158; asm: 808; makefile: 801; javascript: 414; lisp: 109; perl: 62; awk: 36; sed: 4; xml: 4
file content (64 lines) | stat: -rw-r--r-- 1,117 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
= Precedence

From highest to lowest, this is the precedence table for ruby.  High precedence
operations happen before low precedence operations.

  !, ~, unary +

  **

  unary -

  *, /, %

  +, -

  <<, >>

  &

  |, ^

  >, >=, <, <=

  <=>, ==, ===, !=, =~, !~

  &&

  ||

  .., ...

  ?, :

  modifier-rescue

  =, +=, -=, etc.

  defined?

  not

  or, and

  modifier-if, modifier-unless, modifier-while, modifier-until

  { } blocks

Unary <code>+</code> and unary <code>-</code> are for <code>+1</code>,
<code>-1</code> or <code>-(a + b)</code>.

Modifier-if, modifier-unless, etc. are for the modifier versions of those
keywords.  For example, this is a modifier-unless statement:

  a += 1 unless a.zero?

Note that <code>(a if b rescue c)</code> is parsed as <code>((a if b) rescue
c)</code> due to reasons not related to precedence. See {modifier
statements}[control_expressions.rdoc#label-Modifier+Statements].

<code>{ ... }</code> blocks have priority below all listed operations, but
<code>do ... end</code> blocks have lower priority.

All other words in the precedence table above are keywords.