So pretty much the data editors types are classes?
Yes, but they are more strict. Although under the hood there are classes, they are also fairly immutable, you notice that values are static, they can not take functions (I can't put a damage effect value to be some combination of other values). This is called Data Oriented Design.
So pretty much the data editors types are classes?
Yes, but they are more strict. Although under the hood there are classes, they are also fairly immutable, you notice that values are static, they can not take functions (I can't put a damage effect value to be some combination of other values). This is called Data Oriented Design.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Yes, but they are more strict. Although under the hood there are classes, they are also fairly immutable, you notice that values are static, they can not take functions (I can't put a damage effect value to be some combination of other values). This is called Data Oriented Design.
Yes, but they are more strict. Although under the hood there are classes, they are also fairly immutable, you notice that values are static, they can not take functions (I can't put a damage effect value to be some combination of other values). This is called Data Oriented Design.