Add a bit of documentation regarding library initialization about joltphysics HOT 4 CLOSED

I've added some documentation. Let me know if it is clear now. And yes, the factory and type registration is boilerplate that every application needs to do once.

from joltphysics.

Thanks, yes it's clearer now! If you don't mind, two quick followups:

1. Is there a case where user code will use Factory instance, or it's just used internally by Jolt?
2. Is there any article/code comment/explanation on the whole Jolt runtime types stuff, like RTTI, which I am not deeply familiar with?

from joltphysics.

Is there a case where user code will use Factory instance, or it's just used internally by Jolt?

Only if you create your own custom shapes and want to serialize them using Jolt's serialization system.

Is there any article/code comment/explanation on the whole Jolt runtime types stuff, like RTTI, which I am not deeply familiar with?

No there isn't, but it is a very common programming pattern and you can find lots of resources online about it. There's not much more to it than that you can at run time get type information for an instance of a virtual class (e.g. the name of the concrete type if you only have a pointer to its base class) and when you have a class name (string) you can construct an instance of the class.

from joltphysics.

Thanks for all explanations.

from joltphysics.