getter

I have a mocked object that is passed as a constructor argument to another object. How can I test that a mocked object's property has been called? This is code I am using currently: INewContactAttributes newContact = MockRepository.GenerateMock<INewContactAttributes>(); newContact.Stub(x => x.Forenames).Return("One Two Three"); someobject.ConsumeContact(newContact); newContact.AssertWasCalled(x => { var dummy = x.Forenames; }); This works except when within the "someobject" the getter on Forenames property is used multiple times. That's when I get "Rhino.Mocks.Exceptions

I'm a bit confused about the use of getter/setters and constructors (see the below code for an example) public class ExampleClass { private int value = 0; public ExampleClass () { value = 0; } public ExampleClass (int i) { this.value = i; } public int getValue() { return value; } public void setValue(int val) { this.value = val; } public static void main(String[] args) { ExampleClass example = new ExampleClass (20); example.setValue(20); //Both lines above do same thing - why use constructor? System.out.println(example.getvalue()); } } All I've learned is that we need getters/setters for

In JavaScript (ES5+), I'm trying to achieve the following scenario: An object (of which there will be many separate instances) each with a read-only property .size that can be read from the outside via direct property read, but cannot be set from the outside. The .size property must be maintained/updated from some methods which are on the prototype (and should stay on the prototype). My API is already defined by a specification so I can't modify that (I'm working on a polyfill for an already-defined ES6 object). I'm mostly trying to prevent people from shooting themselves in the foot

This works in modern Chrome/Firefox/Opera but fails in IE8. Haven't tried it in IE9. How can I make this cross-browser compatible, including IE7+? (Fiddle here.) var foo = { get test(){ return 'Works'; } }; // foo.test should be 'Works' I've seen some usage with __defineGetter__ but that threw an 'unrecognized method' error in IE8. I don't believe you can. In IE8 and lower, property access is mere property access. There's no way to run function code without explicitly invoking the function. I think in IE8 you may be able to with DOM elements, but I don't believe it works for regular native

the best way to explain is with example so: this is the model public class Person { public int age; public string name; } this is the view model public class PersonVM { } my question is: should the vm expose the person to the data template or encapsulate the model properties with his own properties? The view model should declare its own properties and hide the specifics of the model from the view. This gives you the most flexibility, and helps keep view model-type issues from leaking into the model classes. Usually your view model classes encapsulate the model by delegation. For example, class

What is the defference if I called NSString *theNameToDisplay = _name; or NSString *theNameToDisplay = self.name; I know it might be a silly question but I see both versions used a lot and I don't spot a difference in the output? Thanks! Assume you have in your .m file this line (and don't have any overriden methods to direct access to _name) @synthesize name = _name; It mean that property name (self.name) will use variable _name when you try to access it. In this case self.name is equal to _name But if you have dynamic property for name, something like this : -(NSString)name{ return @"1234";

I have a class as follows: class Foo : PropertyChangedBase { private int _property; public int Property { get { return _property; } set { OnAssignPropertyChanged("Property", () => _property, value); } } PropertyChangedBase implements INotifyPropertyChanged with the following methods: protected void OnAssignmentPropertyChanged<T>(string propertyName, Expression<Func<T>> fieldExpression, T value) { var get = fieldExpression.Compile(); if (get().Equals(value)) { return; } // invoke set property method SetProperty(fieldExpression, value); PropertyChanged?.Invoke(this, new PropertyChangedEventArgs