Talk:Data Types

Why would Vector2 and Vector3 be related at all? UDim2 is composed of 2 UDim values (X and Y). BrickColor has a Color3 property (Color). But Vector3 does not contain a Vector2 and Vector2 definately does not contain a Vector3. --GoldenUrg 22:15, 30 May 2010 (UTC)

I don't see any need to place these into a hierarchy. Vector3 is a basic object used for a lot of functions independent of CFrame. Nor do we need to explain CFrame here. --GoldenUrg 05:20, 31 May 2010 (UTC)

Since when is the rotational matrix on the data type list. Its a component of CFrame, not its separate data type. I vote to remove it from the list since it is already explained on the CFrame page. --Camoy 12:04, 31 May 2010 (UTC)

Is the nesting supposed to show composition, or inheritance? Only I'd say that Vector3s are derived from Vector2s, whereas UDim2s are composed from two UDims.

NXTBoy (talk • contribs)

14:27, 31 May 2010 (UTC)

I think it's supposed to show composition. --Blocco|^{Userpage-Talkpage} 14:49, 31 May 2010 (UTC)

I first put them like that because they're somewhat related :P You guys are thinking way too much into it. Vector3s are not derived from Vector2s. A Vector2 is a Vector3 without the Z component. That's seriously it. Same UDim and UDim2.

It's not the same as UDim2. UDim2 actually contains 2 UDim type objects. Why not just make the list flat? Does having 2 items indented help anyone with understanding these terms? --GoldenUrg 02:54, 1 June 2010 (UTC)

Additionally, Rotation Matrix is not a data type, and should not be present. I'll take it out. ---Mr Doom Bringer 17:37, 31 May 2010 (UTC)

Is Content a data type? --Blocco|^{Userpage-Talkpage} 01:52, 24 June 2010 (UTC)

Also, where would Userdata go as a data type? It definitely is one. --Blocco|^{Userpage-Talkpage} 23:33, 29 June 2010 (UTC)