That interview question reflects a certain belief of the person asking the question. I believe that the person is wrong, and therefore you can go one of two directions. Give them the answer they want. Respectfully disagree. The answer that they want, well, the other posters have highlighted those incredibly well. Multiple interface inheritance, the … Read more
I could be wrong, but I think this may be something to do with the way classes are instantiated in VBA. For example: Dim oClass1 as Class1 Set oClass1 = new Class1 Is different than Dim oClass1 as New Class1 In the second case I believe the constructor doesn’t get called until the property is … Read more
Edit 2: I had another potential thought here: You mentioned that you are running on x64. I’ve tested this same issue on x86, and seen the same performance when using auto-properties vs. fields. However, if you look around on Connect and mailing list/forum posts, there are many references online to the fact that the x64 … Read more
There are two different ways to implement the approach based on class methods: Make a singleton instance using a class hidden from everybody, and hide its methods behind wrapper class methods with identical signatures, or Make class methods that do all the work The implications of the first implementation are that everything you can do … Read more
I think your intuition is about right. Historically, callable objects (or what I’ve sometimes heard called “functors”) have been used in the OO world to simulate closures. In C++ they’re frequently indispensable. However, __call__ has quite a bit of competition in the Python world: A regular named method, whose behavior can sometimes be a lot … Read more
In the classical (OO) inheritance pattern, the static methods do not actually get inherited down. Therefore if you have a static method, why not just call: SuperClass.static_method() whenever you need it, no need for JavaScript to keep extra references or copies of the same method. You can also read this JavaScript Override Patterns to get … Read more
Returning a value is preferable as it allows you to keep all the attribute modifying in one place (__init__). Also, this makes it easier to extend the code later; suppose you want to override _build_query in a subclass, then the overriding method can just return a value, without needing to know which attribute to set. … Read more
There are rare, but very good, reasons to use method hiding. Eric Lippert posted a great example on his blog: interface IEnumerable<T> : IEnumerable { new IEnumerator<T> GetEnumerator(); } However, I think hiding should be the exception, and only used sparingly.
You should be able to create a reference to your survey before you iterate over the questions. function Survey() { this.questions = new Array(); var survey = this; $(‘.question’).each(function(i) { survey.questions.push(new Question(this)); }); } function Question(element) { this.element = $(element); } var survey = new Survey(); $.each(survey.questions, function() { $(“ul”).append(“<li>” + this.element.text() + “</li>”); }); … Read more