forked from Ortham/libloadorder
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[7.2.0]LoadOrder::CheckValidity() drop master/children order check:
Closes #7. Dropping out of order warn (for now at least): The library is too low level (Wrye Bash allows out of order masters for instance) + GetMasters is extra file IO. Note also that ActivePlugins did not check (asymmetry). Moreover lo_fix_plugin_lists did not fix this, leading to the stack overflows described in: Ortham#16 This should be re-added as a weak warning - again will be addressed in liblo 8+ on unifying LO and active loading. LoadOrder::CheckValidity() changed to check as much as possible instead of throwing at first error Not sure about my way of deleting the file pointer - my C++ is rusty. Under #3: cache masters and existence checks !!! Current cache is a monkey patch, but the obvious cache key (Name, size, modtime) would fail for instance on esm flip by wrye bash.
- Loading branch information
Showing
4 changed files
with
41 additions
and
34 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters