Scope issue with javascript.

Please support our JavaScript / DHTML / AJAX advertiser: PostgreSQL or MySQL? Compare and contrast the two most popular open source databases
Reply

Join Date: Dec 2007
Posts: 31
Reputation: AaronASterling is an unknown quantity at this point 
Solved Threads: 5
AaronASterling's Avatar
AaronASterling AaronASterling is offline Offline
Light Poster

Scope issue with javascript.

 
0
  #1
Apr 12th, 2008
Hello,

I am messing around with javascript. I am trying to create a function to which i can pass a constructor and recieve back an object. Kinda (read exactly) like the new keyword. call it a learning exercise. I have a working model but i don't like it. here it is

  1. function CREATE(constructor) {
  2. var o = new constructor();
  3. if (arguments.length > 1) {
  4. constructor.apply(o, Array.prototype.slice.apply(arguments, [1]));
  5. }
  6. return o;
  7. }

I don't like it because it uses the new keyword on the constructor and then calls the constructor again if there are any arguments to be passed on it. kinda stupid. More importantly its not what i first wrote and since i don't understand why what i first wrote doesn't work, im agrivated. What I want is
  1. function CREATE(constructor) {
  2. var o = new Object();
  3. o.prototype = constructor.prototype;
  4. if (arguments.length > 1) {
  5. constructor.apply(o, Array.prototype.slice.apply(arguments, [1]));
  6. }
  7. return o;
  8. }

here is some test code to illustrate how this breaks....

JavaScript / DHTML / AJAX Syntax (Toggle Plain Text)
  1. function TestConstructor(value) {
  2. this.value = this.dummy(value);
  3. }
  4.  
  5. TestConstructor.prototype.dummy = function (value) {
  6. return value;
  7. };
  8.  
  9. var testObject = CREATE(TestConstructor, 1);

javascript says that dummy does not exists. I run it in firebug and just before the this.value = this.dummy(value); line is run, this is an object that has a prototype member and that prototype member has a dummy method. From what i understand, javascript should try to find dummy as a method of this , fail, then look for it as a member of this.prototype and succeed. I can see that it is there in firebug. Does anyone have any idea what is going on?

Thanks,
Aaron.
Aaron Sterling
Reply With Quote Quick reply to this message  
Join Date: Dec 2007
Posts: 31
Reputation: AaronASterling is an unknown quantity at this point 
Solved Threads: 5
AaronASterling's Avatar
AaronASterling AaronASterling is offline Offline
Light Poster

Re: Scope issue with javascript.

 
0
  #2
Apr 12th, 2008
Ok...when i change the line this.value = this.dummy(value) to this.value = this.prototype.dummy(value) the code runs. Does anybody have any idea what this is about? isn't the point of the prototype member that methods and members contained in it can be accessed indirectly as I was originally trying to do? there is deep understanding awaiting anyone that wants to come and play with me.
Aaron Sterling
Reply With Quote Quick reply to this message  
Join Date: Jun 2006
Posts: 7,649
Reputation: ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of 
Solved Threads: 474
Super Moderator
Featured Poster
~s.o.s~'s Avatar
~s.o.s~ ~s.o.s~ is offline Offline
Failure as a human

Re: Scope issue with javascript.

 
0
  #3
Apr 12th, 2008
> Ok...when i change the line this.value = this.dummy(value) to this.value =
> this.prototype.dummy(value) the code runs.

Are you sure this works, because IMO it shouldn't. Try to instantiate your object in a normal manner and see this line blow up. The prototype property of the object is not the same as the prototype property of the Constructor object. Each object created using a constructor has an *implicit* reference to it's Constructors' prototype. It works in your case because in your CREATE function you end up assigning the prototype property of the Constructor object (TestConstructor) to the prototype property of the newly created object.

The only way to make your dummy() function not blow up is to call it as TestConstrutror.prototype.dummy() and not this.prototype.dummy() for the reasons mentioned above.

As far as your issue is concerned, I think that as long as an object isn't created, the context for property lookup using the prototype chain is not set up. So when the call to dummy function inside the constructor is made, a implicit link has not been set up between the object which is *yet to be created* and the prototype property of the Constructor. This can be verified by the fact that once the Constructor exits and a new object is returned, the call to dummy() works as it should. E.g.
JavaScript / DHTML / AJAX Syntax (Toggle Plain Text)
  1. TestConstructor.prototype.dummy = function (value) {
  2. return value * 2;
  3. };
  4.  
  5. function TestConstructor(value) {
  6. this.value = this.prototype.dummy(value); // won't work
  7. };
  8.  
  9. var a = new TestConstructor(1);
  10. a.dummy(); // This works!

Just my 2 cents...
I don't accept change; I don't deserve to live.

Jo Tujhe Jagaaye, Nindein Teri Udaaye Khwaab Hai Sachcha Wahi.
Nindon Mein Jo Aaye Jise To Bhul Jaaye Khawab Woh Sachcha Nahi.
Khwaab Ko Raag De, Nind Ko Aag De
Reply With Quote Quick reply to this message  
Join Date: Jan 2007
Posts: 3,210
Reputation: MidiMagic has a spectacular aura about MidiMagic has a spectacular aura about 
Solved Threads: 165
MidiMagic's Avatar
MidiMagic MidiMagic is offline Offline
Nearly a Senior Poster

Re: Scope issue with javascript.

 
0
  #4
Apr 14th, 2008
The thing that you don't see is that the object is created globally. The thing passed around in the function calls is a pointer to the object, not the object itself.
Last edited by MidiMagic; Apr 14th, 2008 at 5:01 pm.
Daylight-saving time uses more gasoline
Reply With Quote Quick reply to this message  
Join Date: Jun 2006
Posts: 7,649
Reputation: ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of ~s.o.s~ has much to be proud of 
Solved Threads: 474
Super Moderator
Featured Poster
~s.o.s~'s Avatar
~s.o.s~ ~s.o.s~ is offline Offline
Failure as a human

Re: Scope issue with javascript.

 
0
  #5
Apr 14th, 2008
> The thing that you don't see is that the object is created globally.

What? Which object? And whatever happened to scoping rules in Javascript?

> The thing passed around in the function calls is a pointer to the object, not the object itself.

You are way off the actual topic under discussion.
I don't accept change; I don't deserve to live.

Jo Tujhe Jagaaye, Nindein Teri Udaaye Khwaab Hai Sachcha Wahi.
Nindon Mein Jo Aaye Jise To Bhul Jaaye Khawab Woh Sachcha Nahi.
Khwaab Ko Raag De, Nind Ko Aag De
Reply With Quote Quick reply to this message  
Join Date: Jan 2007
Posts: 3,210
Reputation: MidiMagic has a spectacular aura about MidiMagic has a spectacular aura about 
Solved Threads: 165
MidiMagic's Avatar
MidiMagic MidiMagic is offline Offline
Nearly a Senior Poster

Re: Scope issue with javascript.

 
0
  #6
Apr 16th, 2008
The scoping rules are slightly different for objects.

With a variable, the scoping is as you would expect it. But with an object (an array or some other kind of construct), the scoping is quite different.

When you pass an object, or part of an object as a function parameter, you are actually sending a pointer that tells where the object is. This usually works as expected, but the function can not return a changed object back through a parameter.
Last edited by MidiMagic; Apr 16th, 2008 at 10:02 pm.
Daylight-saving time uses more gasoline
Reply With Quote Quick reply to this message  
Join Date: Dec 2007
Posts: 31
Reputation: AaronASterling is an unknown quantity at this point 
Solved Threads: 5
AaronASterling's Avatar
AaronASterling AaronASterling is offline Offline
Light Poster

Re: Scope issue with javascript.

 
0
  #7
Apr 16th, 2008
Originally Posted by MidiMagic View Post
When you pass an object, or part of an object as a function parameter, you are actually sending a pointer that tells where the object is. This usually works as expected, but the function can not return a changed object back through a parameter.

  1. function modifyObject(o) {
  2. o.value = 'Bullocks to that';
  3. return o;
  4. }
  5.  
  6. obj = new Object();
  7. alert((modifyObject(obj)).value);
Last edited by AaronASterling; Apr 16th, 2008 at 10:33 pm. Reason: forgot a closing paren in the code
Aaron Sterling
Reply With Quote Quick reply to this message  
Reply

This thread is more than three months old.
Perhaps start a new thread instead?
Message:



Other Threads in the JavaScript / DHTML / AJAX Forum


Views: 1718 | Replies: 6
Thread Tools Search this Thread



Tag cloud for JavaScript / DHTML / AJAX
About Us | Contact Us | Advertise | DaniWeb | Acceptable Use Policy | RSS Feed

©2003 - 2009 DaniWeb® LLC