🚀 go-pugleaf

Wrong question.  Any Object passed into a function is just a local reference
the the main object.  You can change your "reference pointer" all you want,
but that wont affect the object.

BAsically

change (boolean ok)
{



}

here "ok" is just a pointer to the original Object or primitive.  You can
make ok point to something new, but that doesent change the original object.
Believe it or not, this is true for C++ and C as well.  They use poionters
to pointers.  Thats what you need to do.

You basically have to wrap your object inside an object.

Class Holder
{
    public Object var;
}


Change(Holder value)
{
    value.var = new Object("new value");
}
That is the ONLY way.

AS you get more familiar with object oriented programming, the need to do
this will disappear.

"Steve Holt" <Steve_Holt@PortaSystems.co.uk> wrote in message
news:3b2a0bc8_2@dnews...
> this doesn't change the value of ok because its passed by value
>
> change(boolean ok)
> {
>     ok = true;    // only has an effect in this methods scope
> }
>
> So I figured using the Boolean class may achive this because its passed by
> reference
>
> change(Boolean ok)
> {
>     // but no method to change value inside the class
> }
>
>
> Please don't ask ne to use the return value as this returns something
else.
> I'm probably going to get it to throw an exception instead but I'm
> interested
> to know how you would do this and why the Boolean class doesn't provide a
> method to change the value - weird if you ask me!
>
>