evaluation-strategy

If a function is called using Call-by-Reference , then any changes made to the variable inside the function are affected immediately to the caller. And for Call-by-Sharing , it is affected at the end of the function. Question 1: Does Java uses Call-by-Sharing instead of Call-by-Reference ? Question 2: I think that Call-by-Sharing differs from Call-by-Reference only while multithreading. It is created only to decrease concurrent over-writing of values while it is being used in some other thread; to provide consistency. Am I right? I would recommend that you don't use "call by sharing"

When I write like this: public class test { void mainx() { int fyeah[] = {2, 3, 4}; smth(fyeah); System.out.println("x"+fyeah[0]); } void smth(int[] fyeah) { fyeah[0] = 22; } } It prints x22; When I write like this: public class test { void mainx() { int fyeah = 5; smth(fyeah); System.out.println("x"+fyeah); } void smth(int fyeah) { fyeah = 22; } } It doesn't print x22, but prints x5. Why, in the second version function, doesn't the value change? Does it change values only for array elements? The fyeah variable in your first example contains a reference to an array (not an array), while the

I know that Scala supports call-by-name from ALGOL, and I think I understand what that means, but can Scala do call-by-reference like C#, VB.NET, and C++ can? I know that Java cannot do call-by-reference, but I'm unsure if this limitation is solely due to the language or also the JVM. This would be useful when you want to pass an enormous data structure to a method, but you don't want to make a copy of it. Call-by-reference seems perfect in this case. Java and Scala both use call by value exclusively, except that the value is either a primitive or a pointer to an object. If your object