MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is julia> 1 + 2 + 3 6 julia> +(1, 2, 3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that Exceptions to be tested for, and for the graceful handling of things that may ordinarily break your application. For example, in the below code the function for square root would normally throw an exception

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is julia> 1 + 2 + 3 6 julia> +(1, 2, 3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that Exceptions to be tested for, and for the graceful handling of things that may ordinarily break your application. For example, in the below code the function for square root would normally throw an exception

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is julia> 1 + 2 + 3 6 julia> +(1, 2, 3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that Exceptions to be tested for, and for the graceful handling of things that may ordinarily break your application. For example, in the below code the function for square root would normally throw an exception

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is like Int (see Overflow behavior). If we had declared our function as fib(n::Int), however, the application CHAPTER 9. FUNCTIONS 75 to BigInt would have been prevented for no reason. In general, you should julia> 1 + 2 + 3 6 julia> +(1, 2, 3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is like Int (see Overflow behavior). If we had declared our function as fib(n::Int), however, the application CHAPTER 9. FUNCTIONS 75 to BigInt would have been prevented for no reason. In general, you should julia> 1 + 2 + 3 6 julia> +(1, 2, 3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is like Int (see Overflow behavior). If we had declared our function as fib(n::Int), however, the application CHAPTER 9. FUNCTIONS 75 to BigInt would have been prevented for no reason. In general, you should julia> 1 + 2 + 3 6 julia> +(1, 2, 3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is julia> 1 + 2 + 3 6 julia> +(1, 2, 3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that Exceptions to be tested for, and for the graceful handling of things that may ordinarily break your application. For example, in the below code the function for square root would normally throw an exception

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is julia> 1 + 2 + 3 6 julia> +(1, 2, 3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that Exceptions to be tested for, and for the graceful handling of things that may ordinarily break your application. For example, in the below code the function for square root would normally throw an exception

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is julia> 1 + 2 + 3 6 julia> +(1, 2, 3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that Exceptions to be tested for, and for the graceful handling of things that may ordinarily break your application. For example, in the below code the function for square root would normally throw an exception

MethodError: objects of type Int64 are not callable Both expressions are interpreted as function application: any expression that is not a numeric literal, when immediately followed by a parenthetical, is julia> 1 + 2 + 3 6 julia> +(1, 2, 3) 6 The infix form is exactly equivalent to the function application form – in fact the former is parsed to produce the function call internally. This also means that Exceptions to be tested for, and for the graceful handling of things that may ordinarily break your application. For example, in the below code the function for square root would normally throw an exception