>>>>>You are right. However, I'm of opinion that you are actually breaking a 'standard rule' here. You are at risk of changing the value of a variable in the calling program. The code should be something like:
>>>>>
>>>>>

lparameters tlEnabled, toObject
>>>>>
>>>>>local loObjectX    && you're already using loObject for another purpose
>>>>>
>>>>>if vartype( m.toObject ) <> "O"
>>>>>	loObjectX = this
>>>>>else
>>>>>	loObjectX = m.toObject
>>>>>endif

>>>>
>>>>No risk at all since I'm using lparameters and not passing variable by reference.
>>>
>>>Ah, but, as far as I know, objects are always passed by reference, because the object type variables are references to actual objects. So if you pass an object by value, you do get a new variable, which still refers to the same object.
>>
>>
>>You're absolutely right. That again proves that Peter is wrong <g>, since two people can only be right at the same time in Hershelle Ostropoller's stories. <g>
>
>Peter is wrong? <g>

We're both right, it's only that you were pointing out something else.

So yes, your example shows that an object variable, when passed by reference, may be pointing to another object or may even become a variable of any other type.

My point was that regardless of how you pass the object variable, it still doesn't create a copy of an object, and that whatever you do to the its PEMs, they do affect the object as if the object was passed by reference, even if you pass it by value.