I've been passing an GUIDManager around in my project to where ever it's been needed, this was causing some problems. I was wondering if making the whole class static would cause any issues? Before I start correcting all reference to this class, I want to make sure that I won't come into some issue in the future.

namespace Pro{
	typedef unsigned int GUID; 
		class GUIDLookup{   
			static unsigned int allocatedBitCount;
			static std::unordered_map<std::string, GUID> nameMapping;
			static std::stack<unsigned int> releasedGUIDs;
			static GUID newGUID();
		public: 
			 
			static GUID newGUID(const std::string& name);
			static void releaseGUID(const std::string& name);
			static void releaseGUID(GUID);
			static GUID getGUIDFromName(const std::string& name);
			static std::string getName(GUID _id);
		}; 
}

I was cleaning up my code and thought one way would be to stop passing around the GUIDManager.

You're right the it is a name/id lookup.

I've also decided to change the name to GUIDLookup

Well as of right now, Lua will refer to an object via it's name, but before Lua performs a required task, it'll get the ID of the name and use when it operates on the C++ code.

The only problem is that the functions that Lua calls at times require the GUIDLookup. All functions that Lua calls must be static, which means I either have to pass the GUIDLookup via Lua's stack or have the GUIDLookup static.

I'm trying to work on my class structure and naming, what's why I keep refactoring my project :P

What would you call my example up above? because it doesn't fit into a Singleton.

I'm trying to work on my class structure and naming, what's why I keep refactoring my project :P

What would you call my example up above? because it doesn't fit into a Singleton.

It was just according to the Singleton pattern there's a static function that returns a instance of the class, which is then called upon.

Instead of mine which is calling static functions of the class.