No, the issue is, stdiobase only imports what it needs to do the static constructor. stdio may import other things that have nothing to do with the static ctor, but may inadvertently make a cycle.
The theory goes, if there is no true dependency cycle (i.e. two independent ctors that depend on eachother to run), then you should be able to split the static ctor into its own module. -Steve ----- Original Message ---- > From: Michel Fortin <[email protected]> > > Le 2010-11-05 à 12:03, Andrei Alexandrescu a écrit : > > > When encountering a similar problem I defined stdiobase.d to break the >dependency cycle. > > But then, don't you lose the assurance that stdio's static variables will be >initialized before another module that depends on std.stdio is initialized? >What guaranties that std.stdiobase will be initialized before my own module? >Perhaps I should import std.stdiobase. > _______________________________________________ phobos mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/phobos
