Doing lazy initialization certainly works, but it would require all
static member access to go through a check for initialization, first.
The cost of this check persists for a statically compiled language; for
a JITted language like C# the access can be rewritten to remove the check.
- Re: order of static constructor ex... BCS
- Re: order of static constructo... Walter Bright
- Re: order of static constructor execution Leandro Lucarella
- Re: order of static constructor execution Bob Jones
- Re: order of static constructor execution Jacob Carlborg
- Re: order of static constructor execution Michel Fortin
- Re: order of static constructor execution Fawzi Mohamed
- Re: order of static constructor execution Robert Clipsham
- Re: order of static constructor execution Robert Clipsham
- Re: order of static constructor execution Regan Heath
- Re: order of static constructor execution Walter Bright
- Re: order of static constructor execution BCS
- Re: order of static constructor execution Fawzi Mohamed
- Re: order of static constructor execution Regan Heath
- Re: order of static constructor execution Walter Bright
- Re: order of static constructor executi... Regan Heath
- Re: order of static constructor ex... Walter Bright
- Re: order of static constructo... Regan Heath
- Re: order of static constructo... Walter Bright
- Re: order of static constructo... Regan Heath
- Re: order of static constructo... Walter Bright