Webmaster Forum / HTML, CSS, Scripts / JavaScript / November 2005

Well, your definition is rather strange from the point of view of any
OOP language ;-)

If you vant to assign a function result, you use:
this.member = someFunction();

If you vant to assign a new object instance, you use:
this.member = new someFunction();

In the listed example you assign a constructor reference to your member
which is rather pointless except some really special occasions.
Presuming I decrypted your original intentions properly:

function StateSuggestions(pSource) {
this.source = pSource;
this.req=new ActiveXObject("Msxml2.XMLHTTP"); // > IE 5.x only !
this.Process = new MyProcess();
this.requestSuggestions = new MyRequestSuggestions();
// ...
}

<snip>

At this point I seem having lost the thread. You know, irrelevant to
JavaScript specifics you have to take a decision who is who in your
object. Say "Object A has instances of object B ans C as its members";
or: "Object C has instances of object A ans B as its members".

The situation when "Object A has an instance of B as a member and B has
an instance of A as a member" are not in common use unless you writing
a "Hacking OOP" book. Could you post a block-scheme of the desired
structure?

[snip]

AFAIK, the problem is here, and your understanding of the "this"
keyword.

Try instead:-

   var INSTANCE=this;

   this.req.onreadystatechange = function() {INSTANCE.Process();};

In rough terms, the value of "this" within a function depends on what
is calling the function.

If I have:-

   myObjInstance.Process()

then "this" is set to "myObjInstance" within the Process function.

However if you just call

   Process()

then "this" refers to the window object in the browser.  I.e. it is as
if you called:-

    window.Process()

In your code, the effect of the assignment expression

    this.req.onreadystatechange = this.Process;

Is to pass a reference to the "Process" function alone, which does not
include the "this." context.

Accordingly when "onreadystatechange" is fired, is is effectively
calling "Process()", not "obj.Process()".

So "this" will point to the window object, which does not have a "req"
property.

The solution provided above uses closures.

Read this article on closures:-

<URL:http://jibbering.com/faq/faq_notes/closures.html>

Regards

Julian Turner