C# Accessors

[deathismyfriend]

Hello I have been using a lot of the get / set accessors.

I was wondering if it is possible to create your own accessors.

Example:

public float _Test = 0;
private float Test
{
    get { return _Test; }
    set { _Test = value; }
    custom1 { // do actions }
    custom2(int value) { // do actions }
}

Anything like the above would be a great help.

 

[GhostWolf]

The first result when searching Google "c# accessors".

Google is your best friend, please abuse it as much as you can...

 

[deathismyfriend]

The first result when searching Google "c# accessors".

Google is your best friend, please abuse it as much as you can...

Yes I already know about google and use it very often.
I know about get / set accessors. From what I read on there though it does not say anything about custom accessors. That is why I asked the question is it possible to make your own accessors ?

 

[Ralle]

It makes no sense to have anything but get/set if you ask me. Accessors are there to allow you to set a value and get a value. That is all. The only way accessors can be used is obj.x = "Test" and Debug.WriteLine(obj.x). There is no other way to use them.

 

[deathismyfriend]

That is ok if it makes no sense. I think it would make coding for me a little easier and look nicer.
My above question was is it possible ?

 

[Ralle]

I have no idea what you actually want. How would this work? Can you give an example?

 

[deathismyfriend]

I would like it to work something like the get / set accessors.

Here is my above example

public float _Test = 0;
private float Test
{
    get { return _Test; }
    set { _Test = value; }
    custom1 { // do actions }
    custom2(int value) { // do actions }
}

Along with get / set I would like to be able to make custom1 and custom2. Change name accordingly by custom1 / 2 will do for example.
I would like for them to be able to take / return values.

Something so I can do this / something like this.

private Vector2 _Test;
public Vector2 Test
{
    get { return _Test; }
    set { _Test = value; }
    X { return _Test.X; } // Just examples.
    Y { return _Test.Y; }
}

// or like this.

public Vector2 Test
{
    get { return _Test; }
    set { _Test = value; }
    getX { return _Test.X; } // Just examples.
    getY { return _Test.Y; }
}

// This would be the most preferred way.

public Vector2 Test
{
    get 
    {
        vector2 { return _Test; }
        x { return _Test.X; } 
        y { return _Test.Y; }
    }
    set 
    { 
        vector2 { _Test= value; }
        x { _Test.X = value; } 
        y { _Test.Y = value; } 
    }
}

 

[Crazed_seal2]

You can add code to accessors!

you can call functions and make local variables inside accessors. I'm pretty sure this is possible.

 

[deathismyfriend]

I thought this looked clear enough sorry.
These are not variables.

        vector2 { _Test= value; }
        x { _Test.X = value; } 
        y { _Test.Y = value; }

Those are an internal accessor

My main point is I want to be able to create custom accessors other than get / set.

 

[Adiktuz]

strictly speaking, for those that I used, accessors = get/set only (on a per instance variable basis)

though I guess adding your own methods that act as "Accessors" is doable... though I'd simply call them methods rather than accessors... since when you access something, it's really only either you want to use it (get) or you want to change it (set)

PS: anyway, can't you test it out yourself?

 

[deathismyfriend]

strictly speaking, for those that I used, accessors = get/set only (on a per instance variable basis)

though I guess adding your own methods that act as "Accessors" is doable... though I'd simply call them methods rather than accessors... since when you access something, it's really only either you want to use it (get) or you want to change it (set)

PS: anyway, can't you test it out yourself?

I'm still quite new to coding. I don't know how to create my own if it is possible. Can you give me an example ?

 

[Adiktuz]

well, have you tried writing and testing the example you posted?

I'm not sure about C#, and I can't test right now but on other languages that I used you can do things like

class class_name
  method/accessor_name
    do thing here
  end
end

basically you make the "accessors" on the classes/types so that any variables for objects/instances of those can now use the "accessor"

so now if you make a variable of that class/type, you can do variable_name.method/accessor_name

then again, it's more fitting to call them methods since accessors are basically methods that are used for get/set...

 

[deathismyfriend]

It always says get / set accessor expected.

 

[Adiktuz]

can you post the exact code?

 

[Ralle]

You are still not showing any use, just the way you want to code them. Check this out:

public class MyClass
{
    private Vector vec = new Vector(2,3);
    public Vector Vec
    {
        get
        {
            return vec;
        }
        set
        {
            vec = value;
        }
    }

    public double X
    {
        get
        {
            return vec.x;
        }
        set
        {
            vec.x = value;
        }
    }

    public double Y
    {
        get
        {
            return vec.y;
        }
        set
        {
            vec.y = value;
        }
    }
}

This would allow you to do something like

var MyInstance = new MyClass();
MyInstance.Vec; // Would return the vector
MyInstance.X; // Would return the vectors X
MyInstance.Y; // Would return the vectors Y
MyInstance.X = 2; // Would set the X of the vector

 

[deathismyfriend]

I'm not sure if this is the correct way to do it.

        static public bool Return(bool b)
        {
            return !b;
        }

        public bool GetBool { get; set; Return; }

@ Ralle
As I have stated I already know how to use the get / set accessors. I want to create custom accessors. Basically to reduce that above code you have to a minimal amount.

 

[Adiktuz]

I think I get it now, it errors since what you're trying to do is add a custom accessor for a variable... which is not allowed since it really doesn't make any sense to do it anyway...

though if for example a vector is accessible via vec, then it's X component should already be directly accessible via something like

Object.vec.x

without needing for an additional accessor or methods...

else, just do what Ralle posted

 

[deathismyfriend]

When using get; set; accessors you can not use something like. this.vec.x
You can only access the vector unless you make something like what ralle did above.
But as you can think that makes a ton of extra code needed.

 

[Adiktuz]

then that's quite a restriction you got there from C#... why not skip the accessors and make custom get/set methods instead? though then again it might return some longer code...

PS: Somehow, sharpdev doesn't wan't to compile that code...

PS 2: can't you just directly use the vector instead?

 

[GhostWolf]

You realize that the term "accessor" is used to describe a get or set operation....right?

What you keep asking is whether you can make normal class methods, and yes, you can make those.

 

[deathismyfriend]

You realize that the term "accessor" is used to describe a get or set operation....right?

What you keep asking is whether you can make normal class methods, and yes, you can make those.

Accessor is not only used to describe get / set

Example the below uses add / remove accessors.

    public event EventHandler MyEvent
    {
        [MethodImpl(MethodImplOptions.Synchronized)]
        add 
        { 
            _myEvent = (EventHandler)Delegate.Combine(_myEvent, value);
        }
        [MethodImpl(MethodImplOptions.Synchronized)]
        remove 
        { 
            _myEvent = (EventHandler)Delegate.Remove(_myEvent, value); 
        }
    }

If you know what I am asking then can you give me an example ?

 

[GhostWolf]

It looks like there are also add and remove accessors that Microsoft in their brilliance didn't write about in the accessors page, however they seem to be used for something specific.

What you wrote is adding functions dynamically to objects. I do not know if this is possible or not in C# (never used it, you can google it if you want), but this is certainly not a good practice nor something very useful.
You should create a class with methods.

 

[deathismyfriend]

I am trying to make my own accessors. If you believe that I am trying to create class methods then please post an example.

 

[GhostWolf]

You cannot make your own accessors.
Now, if you want something that is possible, and done by everyone else, then use methods.
If you need an example on how to use methods or a class, then go google any beginner C# tutorial.

 

[Magtheridon96]

What problem are you trying to solve with custom accessors?

Never lose focus of the big picture.

Remember, if a feature X doesn't solve any problems, then it might as well not exist.
I'll accept aesthetic purposes, but you need to demonstrate what you gain from doing this.

Also, I don't like the word "possible".
It's possible to write a C or a C++ program with Pascal syntax by abusing macros. Should you? No.