+- Cuberite Forum (https://forum.cuberite.org)
+-- Forum: Cuberite (https://forum.cuberite.org/forum-4.html)
+--- Forum: Development (https://forum.cuberite.org/forum-13.html)
+--- Thread: Why do we need 3 Vector3 types? (/thread-2009.html)
RE: Why do we need 3 Vector3 types? - worktycho - 06-16-2015
If needing an interpreter is a problem, have a look at Perl. It has been proven that parsing Perl is equivalent to the halting problem, and functions can be created at runtime so it could give you a lot of trouble.
RE: Why do we need 3 Vector3 types? - SamJBarney - 06-16-2015
Well, the problem isn't the interpreter; it's trying to get low-level code to do the same thing as the interpreter without a VM.
Runtime function generation will definitely not be a problem
RE: Why do we need 3 Vector3 types? - worktycho - 06-16-2015
How about reflection?
RE: Why do we need 3 Vector3 types? - SamJBarney - 06-16-2015
Reflection will be a little harder to implement, but still possible.
RE: Why do we need 3 Vector3 types? - worktycho - 06-16-2015
I think I need to see more detail, though I still suspect that the alternative paradigms will cause you trouble.
RE: Why do we need 3 Vector3 types? - SamJBarney - 06-16-2015
Probably, but it will still be fun and useful