Problem with shared libraries, exceptions, and global constructors

[Gabriel Dos Reis]

Fergus Henderson <fjh@cs.mu.oz.au> writes:

[...]

| Obviously if there is a real cyclic initialization dependency, where
| global variable x needs to be initialized before global variable y and
| vice versa, then that is a programming error.  But if a cycle occurs
| merely because fine-grained non-circular dependencies at the level of
| individual variables have been conflated at the level of shared objects,
| thus introducing a coarse-grained circularity, then it does not
| necessarily indicate any design error or programming error.  The system
| should support this.

Exactly.  This is what I was referring to when I wrote "from a
compiler implementor point of view".

-- Gaby