On 11/12/2013 1:46 PM, Martin Nowak wrote:
On Sunday, 10 November 2013 at 19:34:32 UTC, Walter Bright wrote:
On 11/10/2013 4:13 AM, Benjamin Thaut wrote:
Actually, it isn't entirely clear to me why the moduleinfo needs to be exported.
That depends on whether using a module might require to link against the
moduleinfo, currently it does. For example there is an importedModules property
in ModuleInfo.
That's only used for initialization order.
The moduleinfo is needed to run the static ctors/dtors, etc., but that is
needed by the code internal to the dll that initializes the dll.
Initialization order is not an issue here, the whole DLL (and all modules) is
initialized before any DLL/exe that depends on it.
Right, so it shouldn't need to list it as an imported module.
