this post was submitted on 27 Jun 2023
7 points (76.9% liked)
C Sharp
1526 readers
2 users here now
A community about the C# programming language
Getting started
Useful resources
- C# documentation
- C# Language Reference
- C# Programming Guide
- C# Coding Conventions
- .NET Framework Reference Source Code
IDEs and code editors
- Visual Studio (Windows/Mac)
- Rider (Windows/Mac/Linux)
- Visual Studio Code (Windows/Mac/Linux)
Tools
Rules
- Rule 1: Follow Lemmy rules
- Rule 2: Be excellent to each other, no hostility towards users for any reason
- Rule 3: No spam of tools/companies/advertisements
Related communities
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This should be a different post, but it depends on what you're planning to do with them. Enums are flexible and could totally make do there regardless of semantic cyclical-ness. Remember with enums you're able to just ignore the values altogether; that's one of the major reasons to use them. If I have a limited list of flags that I use directly in code, they don't have to change at runtime, and don't need additional data associated to them (like 'number of days' or something similar), I'll use an enum.
If you wanted to actually cycle though them in your code, it might be clearer to use both a manager class with a enum. Inside the class, you could use a something like a CurrentSeason property and have a NextSeason, PreviousSeason method to cycle through them. Using modular arithmetic would allow you to change the number of items to cover future features like seasonal transitions or something without having to modify any of your code.
I was employing subtlety as a strong suit. Wasn't it obvious?