Menu
I figured out by trying that
struct PropertyTest
{
@property int x() { return val; }
@property void x( int newVal ) { val = newVal; }
void test()
{
int j;
j = x;
x = 5;
}
private:
int val;
}
does exactly the same when I leave the @property out. Everything compiles fine. What's the point then for declaring functions as @property?
BTW, I'm using the dmd2 compiler.
925
Python's property() is the Pythonic way to avoid formal getter and setter methods in your code. This function allows you to turn class attributes into properties or managed attributes. Since property() is a built-in function, you can use it without importing anything.
The %d specifies that the single variable is a decimal integer. The %n is a platform-independent newline character.
Consider using a property if the member represents a logical attribute of the type. Do use a property, rather than a method, if the value of the property is stored in the process memory and the property would just provide access to the value.
Properties enable a class to expose a public way of getting and setting values, while hiding implementation or verification code. A get property accessor is used to return the property value, and a set property accessor is used to assign a new value.
The reason they work without @property is because @property was added after they allowed the property method syntax. Adding -property to your DMD command line enforces use of @property annotation. It's not the default for backward compatibility reasons. Someday it will become the default (or so they say) so it's best to compile with -property to ensure you are annotating properly.
100
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
