bogus.cc File Reference

#include <core/id/bogus.hh>
#include <core/id/AtomID.hh>
#include <core/id/DOF_ID.hh>
#include <core/id/NamedAtomID.hh>
#include <core/id/TorsionID.hh>

Namespaces
	core
	A class for reading in the atom type properties.
	core::id

Functions
AtomID const	core::id::GLOBAL_BOGUS_ATOM_ID (AtomID::BOGUS_ATOM_ID())
AtomID const	core::id::GLOBAL_CHAINBREAK_BOGUS_ATOM_ID (AtomID::CHAINBREAK_BOGUS_ATOM_ID())
StubID const	core::id::GLOBAL_BOGUS_STUB_ID (StubID::BOGUS_STUB_ID())
void	core::id::initialize_core_id_globals ()
	Calling this function ensures that all of the global variables in core::id are initialize before they are needed. More...

Variables
DOF_ID const	core::id::GLOBAL_BOGUS_DOF_ID (AtomID::BOGUS_ATOM_ID(), PHI)
	Global – may not be used until after core::init is called. More...
NamedAtomID const	core::id::GLOBAL_BOGUS_NAMED_ATOM_ID (NamedAtomID::BOGUS_NAMED_ATOM_ID())
	Globals – may not be used until after core::init is called. More...
NamedAtomID const	core::id::GLOBAL_CHAINBREAK_BOGUS_NAMED_ATOM_ID (NamedAtomID::CHAINBREAK_BOGUS_NAMED_ATOM_ID())
TorsionID const	core::id::GLOBAL_BOGUS_TORSION_ID (TorsionID::BOGUS_TORSION_ID())
	Globals. More...

Detailed Description

Author

Andrew Leaver-Fay

Fix the static-initialization-order fiasco w/ global variable initialization Previously, these globals were in separate compilation units, and the order of their initialization was not guaranteed. Putting them into a single compilation unit fixes that.