Technical interviews

[wonderboy]

Wait, I see it. () is your voodoo on the fly, shot in the arm for unreadable code, function declaration. Appvar2 is the declaration. Appvar1 is the ref, so in theory this is being injected, and the reference holds outside the function declaration.

The constructor function pointer is also set inside the first function declaration.

tulipty question really. To emphasise the manner of object references, there should really be some code after all this performs an operation on appvar1 that was defined on appvar2.

IMVHO.

I think the question is fine. It checks core understanding of basic concepts. That is if the interviewer himself does too...

[Bunk]

Ok not seeing how appVar1 and appVar2 are in any way related? Can we clear this up before we deal with scope?

Ta.

I've spaced it out to explain each part.

var appVar1 = {};

Creates a new global variable called appVar1 and initialises it as an object literal.

(

We'll come back to this bit.

function(appVar2){

  appVar2.MyConstructor = function() {
    //...
  };
}

Create an anonymous function which takes a parameter appVar2 and adds a function MyConstructor to it.

)

(appVar1);

Now we close that opening bracket that I said we'd come back to. This makes the block of code a function expression instead of a function declaration. This is then immediately invoked by the following (appVar1); which passes the object literal appVar1 to the function. This all has the result of adding MyConstructor to appVar1.

[suityou01]

I've spaced it out to explain each part.

var appVar1 = {};

Creates a new global variable called appVar1 and initialises it as an object literal.

(

We'll come back to this bit.

function(appVar2){

  appVar2.MyConstructor = function() {
    //...
  };
}

Create an anonymous function which takes a parameter appVar2 and adds a function MyConstructor to it.

)

(appVar1);

Now we close that opening bracket that I said we'd come back to. This makes the block of code a function expression instead of a function declaration. This is then immediately invoked by the following (appVar1); which passes the object literal appVar1 to the function. This all has the result of adding MyConstructor to appVar1.

Nice post Bunk. Thanks.

I think calling a method a constructor was confusing me as constructors are special. This is agin why I think the question could be better.

Makes sense to me, as much as slippety-sloppety loosely typed, declare anywhere voodoo code ever will.

[wonderboy]

I think calling a method a constructor was confusing me as constructors are special. This is agin why I think the question could be better.

I believe they named the property "MyConstructor" for this very reason.

[Bunk]

Nice post Bunk. Thanks.

I think calling a method a constructor was confusing me as constructors are special. This is agin why I think the question could be better.

Makes sense to me, as much as slippety-sloppety loosely typed, declare anywhere voodoo code ever will.

Not in Javascript

function myFunction() {
  console.log('in the function');
  this.something = 'Hello';
}

myFunction();
// Call the function
// outputs 'in the function'

var myObj = new myFunction();
// Creates an object using the function as constructor

console.log(myObj.something);
// outputs 'Hello'

[barrydidit]

Makes sense to me, as much as slippety-sloppety loosely typed, declare anywhere voodoo code ever will.

Now you can add JS to BS on your CV

[TestMangler]

Now you can add JS to BS on your CV

Fairly sure he had BS on his cv already.....all versions, many years experience