Due to wrong initial design of class ModuleLoader errors displayed when loading library fails miss OS-specific information about a reason of a failure (no such file, invalid format, unresolved external reference, etc.), they only say - module/library not loaded. This makes fixing related bugs extremely problematic in many cases.
Errors reported should be extended in order to show exact reason of a failure.
Messages are enhanced except deprecated UDFs and unfortunately ICU - in case of failure ICU is attempted to be loaded >50 times and reporting all errors to user is definitely unreal.
Submitted by: @AlexPeshkoff
Due to wrong initial design of class ModuleLoader errors displayed when loading library fails miss OS-specific information about a reason of a failure (no such file, invalid format, unresolved external reference, etc.), they only say - module/library not loaded. This makes fixing related bugs extremely problematic in many cases.
Errors reported should be extended in order to show exact reason of a failure.
Commits: 6a63c3b 2d973b9
====== Test Details ======
Thanks to Alex for suggestion about implementation.
The text was updated successfully, but these errors were encountered: