Should I use enums here?

Question

C++ / C#

I was looking for projects to parse and found this code:
It seems to me that instead of classes there should be enums here?

Answer 1

Worth it, it will be more convenient and understandable.

namespace TryEnum
{
    enum DownloadType
    {
        Video, Audio, Custom, Unknown, Default
    }
    enum ForceIpProtocol
    {
        IPv4, IPv6
    }
    enum ProxyProtocol
    {
        HTTPS, HTTP, SOCKS4, SOCKS5
    }
}

And to use like this:

And about interfaces... Interfaces should not be instead of classes; the class implements the interface (the syntax looks like inheritance , but this is not quite inheritance, there is a slightly different implementation). And the interface is needed if you need to implement polymorphism in the code and / or to simplify access to public fields in classes that implement this interface. For example: we have many classes with different implementations, but they all share the same properties (for example, public string Name ( get; set; ); public int Age( get; set; ); etc...) . The interface in this case is needed so that through it we get access to multiple behavior, using different classes containing properties of the same name, without producing code. For clarity:class ClassName : IClassName
we have the Create() method; in which we want to create new people

static void Create()
        {
            // empty...
        }

There are different classes that create a Human and implement the IHuman interface

class SimpleHuman : IHuman
    {
        public string Name { get; set; }
        public int Age { get; set; }
        public SimpleHuman()
        {
            Name = "Generic human...";
            Age = 20;
        }
        public SimpleHuman(string name) : this()
        {
            Name = name;
        }
        public SimpleHuman(string name, int age) : this()
        {
            Name = name;
            Age = age;
        }
    }

class CoolHuman : IHuman
    {
        public string Name { get; set; }
        public int Age { get; set; }
        public CoolHuman()
        {
            Name = "BOB!";
            Age = 20;
        }
        public CoolHuman(string name) : this()
        {
            Name = name;
        }
        public CoolHuman(string name, int age) : this()
        {
            Name = name;
            Age = age;
        }
    }

interface IHuman
    {
        string Name { get; set; }
        int Age { get; set; }
    }

And now, thanks to the implementation of the interface in these classes, we can conveniently use this very interface, for example:

class Create
    {
        public IHuman Human { get; set; }
        public Create()
        {
            Human = new CoolHuman();
        }
        public void Hello()
        {
            Console.WriteLine("Hello, {0}. Today you are {1} years old", Human.Name, Human.Age);
        }
    }

Specifically, in your case, the interface is not needed.

Answer 2

programming is an interesting thing - does it work? Do not touch!

It seems to me that instead of classes there should be interfaces here?

in the text of the question

Should I use enums here?

you already decide in the Wishlist:
- transfers?
- interfaces?
- both?
.. why? (c) from a good anecdote
and the moral is simple - if you understand why? cut, test, use!
ps from the outside, all this is impossible to evaluate without detailed usage scenarios