precedence as +. The only explicitly disallowed names for variables are the names of built-in statements: 10.2. STYLISTIC CONVENTIONS 29 julia> else = false ERROR: syntax: unexpected "else" julia> VersionNumber object, and therefore one can define some version- specific behavior using simple statements as: if v"0.2" <= VERSION < v"0.3-" # do something specific to 0.2 release series end Note that 98 CHAPTER 16. CONTROL FLOW "negative..." end "positive!" Note that very short condi�onal statements (one-liners) are frequently expressed using Short-Circuit Evalua�on in Julia, as outlined in the

precedence as +. The only explicitly disallowed names for variables are the names of built-in statements: 11.2. STYLISTIC CONVENTIONS 31 julia> else = false ERROR: syntax: unexpected "else" julia> VersionNumber object, and therefore one can define some version- specific behavior using simple statements as: if v"0.2" <= VERSION < v"0.3-" # do something specific to 0.2 release series end Note that 100 CHAPTER 17. CONTROL FLOW "negative..." end "positive!" Note that very short condi�onal statements (one-liners) are frequently expressed using Short-Circuit Evalua�on in Julia, as outlined in the

precedence as +. The only explicitly disallowed names for variables are the names of built-in statements: 10.2. STYLISTIC CONVENTIONS 29 julia> else = false ERROR: syntax: unexpected "else" julia> VersionNumber object, and therefore one can define some version- specific behavior using simple statements as: if v"0.2" <= VERSION < v"0.3-" # do something specific to 0.2 release series end Note that 98 CHAPTER 16. CONTROL FLOW "negative..." end "positive!" Note that very short condi�onal statements (one-liners) are frequently expressed using Short-Circuit Evalua�on in Julia, as outlined in the

precedence as +. The only explicitly disallowed names for variables are the names of built-in statements: 10.2. STYLISTIC CONVENTIONS 29 julia> else = false ERROR: syntax: unexpected "else" julia> VersionNumber object, and therefore one can define some version- specific behavior using simple statements as: if v"0.2" <= VERSION < v"0.3-" # do something specific to 0.2 release series end Note that 98 CHAPTER 16. CONTROL FLOW "negative..." end "positive!" Note that very short condi�onal statements (one-liners) are frequently expressed using Short-Circuit Evalua�on in Julia, as outlined in the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Mixing multiple using and import statements . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Handling name conflicts . . . . . . . VersionNumber object, and therefore one can define some version-specific behavior using simple statements as: if v"0.2" <= VERSION < v"0.3-" # do something specific to 0.2 release series end 62 CHAPTER 82 CHAPTER 9. CONTROL FLOW "negative..." end "positive!" Note that very short conditional statements (one-liners) are frequently expressed using Short-Circuit Evaluation in Julia, as outlined in

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Mixing multiple using and import statements . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Handling name conflicts . . . . . . . VersionNumber object, and therefore one can define some version-specific behavior using simple statements as: if v"0.2" <= VERSION < v"0.3-" # do something specific to 0.2 release series end Note that 82 CHAPTER 9. CONTROL FLOW "negative..." end "positive!" Note that very short conditional statements (one-liners) are frequently expressed using Short-Circuit Evaluation in Julia, as outlined in

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Mixing multiple using and import statements . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Handling name conflicts . . . . . . . VersionNumber object, and therefore one can define some version-specific behavior using simple statements as: if v"0.2" <= VERSION < v"0.3-" # do something specific to 0.2 release series end 62 CHAPTER 82 CHAPTER 9. CONTROL FLOW "negative..." end "positive!" Note that very short conditional statements (one-liners) are frequently expressed using Short-Circuit Evaluation in Julia, as outlined in

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Mixing multiple using and import statements . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Handling name conflicts . . . . . . . VersionNumber object, and therefore one can define some version-specific behavior using simple statements as: if v"0.2" <= VERSION < v"0.3-" # do something specific to 0.2 release series end 62 CHAPTER 82 CHAPTER 9. CONTROL FLOW "negative..." end "positive!" Note that very short conditional statements (one-liners) are frequently expressed using Short-Circuit Evaluation in Julia, as outlined in

VersionNumber object, and therefore one can define some version-specific behavior using simple statements as: if v"0.2" <= VERSION < v"0.3-" # do something specific to 0.2 release series end CHAPTER CHAPTER 9. CONTROL FLOW 77 "negative..." end "positive!" Note that very short conditional statements (one-liners) are frequently expressed using Short-Circuit Evaluation in Julia, as outlined in || operators. This behavior is frequently used in Julia to form an alternative to very short if statements. Instead of if end, one can write && (which could be read

VersionNumber object, and therefore one can define some version-specific behavior using simple statements as: if v"0.2" <= VERSION < v"0.3-" # do something specific to 0.2 release series end CHAPTER CHAPTER 9. CONTROL FLOW 77 "negative..." end "positive!" Note that very short conditional statements (one-liners) are frequently expressed using Short-Circuit Evaluation in Julia, as outlined in || operators. This behavior is frequently used in Julia to form an alternative to very short if statements. Instead of if end, one can write && (which could be read