JavaScript pen objects with replaceable nibs

Question

I have a JavaScript question. Imagine a virtual pen. There are many different possible nibs the pen can have, although the pen can only have one nib. I want to create a pen object and then assign it a nib. The nib needs to access the properties and methods of the pen.

This is probably a well-known design pattern. What is the name of this design pattern?

function Pen() {
 var p1=5;
 this.nib=null;
}
function Nib1() {
 // needs access to p1.
}
function Nib2() {
 // needs access to p1.
}
var p = new Pen();
var n1 = new Nib1();
p.nib = n1;
// n1 needs access to p1

• K. Kirsz: I honestly believe there is no such pattern because it is not a good design at all. If anything i would consider this an antipattern. It creates circular dependencies between those classes (because you say Nib needs access to Pen, but why?), which is always a bad thing. Things like Strategy pattern are supposed to address such problems.
• K.F: What did you mean by "needs access to p1", generally the access is unidirectional to avoid circular dependency whenever possible (en.wikipedia.org/wiki/Circular_dependency). Maybe these thoughts on OOP concepts would help you ? (adobe.com/devnet/actionscript/learning/oop-concepts/… or stackoverflow.com/questions/2218937/…) I have a feeling you're just looking for "Composition" , where Pen has-a Nib, and Nib depends on some information that Pen passes into Nib's functions.
• Matthew Brent: I'm not sure if you're making a strange analogy or you want to create a pen in js. You typically want to stay away from this type of co-dependant relationship...try looking at functional programming and closure. It's a solid way to use JS. Going down the whole OOP route with JS can get messy pretty fast.
• TheHans255: I wouldn't say this is a JavaScript question so much as it is a general design question - this is probably a better fit for softwareengineering.stackexchange.com
• Robert Harvey: "Name that thing" doesn't make for a very good question on SO. Perhaps you could describe your specific problem instead?

Answer 1

It sounds a bit like using a constructor. This chapter describes a similar situation but with rabbits instead of pens: http://eloquentjavascript.net/06_object.html#constructors.

The pen would be the constructor:

function Pen(nib) {
 // shared scope
 this.nib = nib;
}

Then you can create

var bluePen = new Pen(blue)

... Although I guess it's slightly different because you're describing a single pen and with the constructor you can end up with multiple instances.