Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Singleton #195

Closed
wants to merge 10 commits into from
Closed

Singleton #195

wants to merge 10 commits into from

Conversation

OldFoolAgain
Copy link
Contributor

This is based off utility PR
In prep for the account merge, two "singletons" were made. Console and Version

Version was made to just be a const std::string wrapper in a stuct (could have been a namespace as well).
Console was made into a singleton.

Starts the unwinding of all the externals in uox3. In console case, it really is a singleton, as you can't have more than one of them.

Also noticed that the thread "cons" was not joined on exit so added that. I think there is still another thread that isn't being joined, but wasn't the focus of this branch.

Essentially no functionality was changed with this at all. For most of the code, Console got a Console::shared(), and the version was renamed and dropped the () on the methods.

This changes all routine calls that wanted a specific type of stream ifstream/ofstream to the generic istream/ostream.  So you can use stringstream, or other derived types.
Modernizes the way LoadResource and SaveResource works in regions.

Added a missing forward declare in MultiMul.h
… just reinitialize the entire vector, based on the default values, and then just update the values that are in the file.
move version as part of transistion, and made it just const std::stirngs

Console was renamed, moved,, and made a singleton
@Xoduz Xoduz added the nomerge - future ref For future reference, not to be merged directly label Oct 10, 2023
@Xoduz Xoduz deleted the branch UOX3DevTeam:0_99_6_RC6 October 14, 2023 13:36
@Xoduz Xoduz closed this Oct 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
nomerge - future ref For future reference, not to be merged directly
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants