getter

问题 I am extending a very simple Java interface from an imported library. The interface is so simple that the only methods it declares are getters and setters for a list of properties. My application is written in Groovy, so I'd like to implement this Java interface with a Groovy class. I was under the impression that Groovy created getters and setters by default for any of its classes' properties - can I use these default getters and setters to satisfy the Java interface's requirements? Library

问题 I'm trying to modify a setter on an attribute Mongoid model, but unlike ActiveRecord, I cannot call super to have Mongoid actually set the attribute, as the model is using include Mongoid::Document rather than a subclass of ActiveRecord::Base . I want to be able to do something like this. class User include Mongoid::Document embeds_one :email_account def email_account=(_email_account) ret = super puts "email account updated!" do_something ret end end except, as its not a subclass, yields

问题 I'm currently learning Java and learning about encapsulation and I'm unsure which of the following is a better practice: Use a getter to return a field value from one class to another and then print it through a method in another class. Call a method in a class from another class to print the value of the field. The value isn't manipulated, only shown through System.out.println(); Any advice would be appreciated :) EDIT: One class (Person) holds information about people, such as name, age,

问题 class Dog { protected $bark = 'woof!'; public function __get($key) { if (isset($this->$key)) { return $this->$key; } } public function __set($key, $val) { if (isset($this->$key)) { $this->$key = $val; } } } What is the point of using these functions. if i can use $dog = new Dog(); $dog->bark = 'woofy'; echo $dog->bark; Why would I bother declaring 'bark' as protected ? Do the __get() and __set() methods in this case effectively make 'bark' public? 回答1: In this case, they do make $this->bark

问题 As I read here http://msdn.microsoft.com/en-us/library/75e8y5dd%28v=VS.100%29.aspx It is possible to have get in an Interface BUT NOT set ? OR if I want getter and setter in Interface, do I have to use the old syntax getVar setVar just because new syntax doesn't fit Interface syntax? Update: If I must omit set in Interface, does this means I cannot enforce class to have setter which defeats the purpose of having an Interface in this case as I can only partially enforce? 回答1: No. I think you

问题 In C# you can create getter/setters in a simpler way than other languages: public int FooBar { get; set; } This creates an internal private variable which you can't address directly, with the external property 'FooBar' to access it directly. My question is - how often do you see this abused? It seems like it has a high potential to violate encapsulation best-practices often. Don't get me wrong, I use it as appropriate, and partial variations of it for read-only write-only types of properties,

问题 In scala there is no difference for the user of a class between calling a method or accessing some field/member directly using val x = myclass.myproperty. To be able to control e.g. setting or getting a field, scala let us override the _= method. But is = really a method? I am confused. Let's take the following code: class Car(var miles: Int) var myCar = new Car(10) println(myCar.miles) //prints 10 myCar.miles = 50 println(myCar.miles) //prints 50 Same goes for this code (notice the double

问题 While working with Node.js, Mongoose and MongoDB, I have found that my Mongoose schema getters and setters do not fire when I perform a findOne query. I have found an old thread that suggests there was an issue with getters and setters in version 2.x, but it states that it has since been resolved and I'm using the very latest version of Mongoose (3.8.7). Here's part of my schema function testGetter(value) { return value + " test"; } /** * Schema */ var schema = new Schema({ username: { type:

问题 I was following a tutorial today that had me scratching my head for an hour. Consider: public class MyClass { public int getTotal() { amount = 100; return amount; } } and an excerpt from a JSP: <p>Total: ${objectOfTypeMyClass.total}</p> //object instantiated elsewhere Nowhere in the code was an instance variable named " total " ever declared or used. The only reference to the word "total" in the whole project (other than in the JSP) was the method getTotal() . So after some desperate last

问题 If you've a domain class in a grails project you can also use getter and setter to write or read them. For example domain class Book has attribute: String author In controller you've a book and you want to set the author for this book: This works with direct access to the attribute or with getter and setter methods although they aren't in the class. book.author = "Mike Miller" book.setAuthor("Mike Miller") What's the preferred way of getting and setting attributes in groovy & grails? 回答1: