Doing something

 Kind of realized that some times, doing something can distract you from getting something done.

I had decided that I needed an interface then found the INumber generic interface. However, I still hadn't done the work to decide what I needed or how I was going to make it work.

So, lets do that now.

What is a number. It is a value, a quantity. Mathematicians have determined that these values have certain properties, main among them, that they can be discussed in a meaningful way separate from the object that they are describing the quantity of. Mathematically 19 oranges, is the same as 19 inches, is the same as 19 days, which is the same as 201₃ math nerds (201₃ is 19 expressed in base 3, will get to bases later) (and you can find 19 math nerds in the same place, though it usually a math class, or a comic con).

So, what does a number data type need. INumber says 50 some functions, and it is right to some degree. However, those functions tell us attributes of the number or defines ways to interact with other numbers, but the most important thing is the value. It is a data type and we need to have the data. What is the data with a number, well the value. So, how do you store the value? Well, that was some of what I wanted to explore with this project. With the OutrageousInt I started with, the value is an int. And yes, I'm wrapping an int in an unnecessary class, but this whole thing is in and of itself, unnecessary. I am doing it to try and learn something, and experiment with algorithms and maybe help someone else.

Now, does the value have any properties, or need any properties to ease calculation or interaction with other classes implementing INumber? Well, that is the question, but perhaps I need to start with a naïve implementation. Currently, I believe that my int version is finished or close to it, so maybe I need to create a unit testing project to be used on the OutrageousNumbers, and perhaps some sort of simple app to play with the numbers. 

Implementing INumber

 I thought it might be useful for some to describe my tool set. I am currently using Visual Studio Community 2022, I typically keep it up to date. I am using .NET 7.0 and C# 11.0. I use Git for version control. I'm using GitHub for storage of the repository and management of the project. I am also currently experimenting with GitHub Copilot for code suggestions and assistance.

My intention is to create a branch for each blog post or perhaps group of blog posts, depending on how tasks, or ideas get broken up. I will then try to check in every major step of the way. The banch for today is, ImplementINumber.

First I will add a Value. because a number has a value. This is not part of the interface, but may be used by the interface. I am using a property because it is a practice that I am used to and is common in the offices that I have worked in. Specifically using what is know as an auto property. Technically any data stored in a class is a field, a property is a set of methods that set the data and get the data. Using methods for access allows for validation and alteration as needed either on setting or getting the data. A standard property is written - 

private int _value;
private int Value
{
  get { return _value; }
  set { _value = value; }
}

I realize that I am explaining things in a haphazard manor. If you feel that I'm being too detailed feel free to skip any description, paragraph, post or the whole blog. If you feel that there is something that you need explained further, please feel free to ask, if I cannot answer I may be able to help you find the answer.

Returning to properties, the previous code snippet is a fairly standard property/field code snippet. If only there were a simpler way to write it that functionality in .NET would be able to replace with the structure above in the background. Well, there is -

private int Value { get; set; }

The backing field is assumed, as is the code for the get and the set. This format does allow for the declaration of the get or set, if it is needed. This is what is known as an auto property.

At this point Quick Actions can be used to create all the interface functions. It seems that there were some limitations on the Quick Actions. But there are other Quick Actions to add more for the interface. I may want to make value protected and not private. I may even end up making my own interface to add properties. But I will finish making the int number first.

I feel like I've lost the plot. I need to reset.