class Foo
{
    const int Bar( const double Naz ) const;
}

-----
const int Bar( const double Naz ) const;
^^^^^^^^^
Returns a constant int
-----
const int Bar( const double Naz ) const;
               ^^^^^^^^^^^^
Requires a constant double
-----
const int Bar( const double Naz ) const;
                                  ^^^^^
Foo::Bar() may not change the instance of Foo that it's called from
Also, Foo::Bar() may be called on constant instances of Foo
-----

Quote:Original post by c4c0d3m0n
const int Bar( const double Naz ) const;
^^^^^^^^^
Returns a constant int

Quote:Original post by c4c0d3m0n
const int Bar( const double Naz ) const;
^^^^^^^^^^^^
Requires a constant double

Quote:Original post by c4c0d3m0n
*grumble* This is why Java confuses me so much, pointers, references, instances, it's all one big pile of steaming foobar.

Quote:Original post by c4c0d3m0n
when I write boolean isUnderPoint(Point p), p is automatically passed by reference (since there is no NULL pointer if I'm not mistaken).

Point p = null;p.doSomething(); // NullPointerException

Quote:
James Gosling, et al., The Java Programming Language, 4th Edition
Some people will say incorrectly that objects are passed "by reference." In programming language design, the term pass by reference properly means that when an argument is passed to a function, the invoked function gets a reference to the original value, not a copy of its value. If the function modifies its parameter, the value in the calling code will be changed because the argument and parameter use the same slot in memory.... The Java programming language does not pass objects by reference; it passes object references by value. Because two copies of the same reference refer to the same actual object, changes made through one reference variable are visible through the other. There is exactly one parameter passing mode -- pass by value -- and that helps keep things simple.

Quote:Original post by c4c0d3m0n
But what if I want to pass a copy of my object to a function? How would I do that? I've had situations in C++ where I had to pass a copy.

foo.someMethod(myObject.clone());

public class CloneExample implements Cloneable{    private int i;    private boolean b;    private int[] a;    private String s;        public CloneExample clone()    {        CloneExample that = null;        try        {            // make a bit by bit copy by calling the inherited clone() method            that = (CloneExample) super.clone();            // a references the original array, so we have to manually clone it            that.a = this.a.clone();            // We don't have to clone s because Strings are immutable.            // this.a and that.a both refer to the same object, but that is no problem.        }        catch (CloneNotSupportedException e)        {            System.err.println("this shouldn't happen");            e.printStackTrace();        }        return that;    }}

Quote:Original post by c4c0d3m0n
Also, why do certain built-in functions of Java give back a copy of a value instead of a reference to it?

Quote:Original post by c4c0d3m0n
I'd actually expect Math.max( i, j ) to return i or j instead of the actual value stored inside the variable.

Quote:Original post by c4c0d3m0n
I think my language of preference will stay C++ for a while, maybe untill I try my heart at another language...