On 28 November 2012 21:08, Jacob Carlborg <doob@me.com> wrote:
On 2012-11-28 16:54, Manu wrote:

Certainly a potential problem, but I've set up my code such that these
static constructors themselves have no external dependencies, and
initialisation order is unimportant, since registered stuff just ends up
in a globally accessible hash table anyway.

It doesn't matter if the static constructors don't have any external dependencies. You can have an empty static constructor in two modules which import each other. That will result in an exception being thrown at runtime.

Well fortunately that hasn't happened yet... That does worry me though. I can't imagine a work-around if that comes up.