1Ra
|
  |
| Joined: 02 May 2010 |
| Total Posts: 2400 |
|
|
| 01 Sep 2011 04:26 PM |
yes or no, is it possible?
X = {Vector3.new(321,31234,4),Vector3.new(231,213,21)} |
|
|
| Report Abuse |
|
|
NXTBoy
|
  |
| Joined: 25 Aug 2008 |
| Total Posts: 4533 |
|
|
| 01 Sep 2011 04:27 PM |
Or you could just, you know, try it?
Yes, it is possible. |
|
|
| Report Abuse |
|
|
1Ra
|
  |
| Joined: 02 May 2010 |
| Total Posts: 2400 |
|
|
| 01 Sep 2011 04:28 PM |
| would take to long short on time thanks. |
|
|
| Report Abuse |
|
|
swmaniac
|
  |
| Joined: 28 Jun 2008 |
| Total Posts: 15773 |
|
|
| 01 Sep 2011 04:35 PM |
| Table's values and keys can be any nonnil value (well technically their values can be nil but it's a really bad idea - it messes with some functions; operator's ability to go through them). |
|
|
| Report Abuse |
|
|
NXTBoy
|
  |
| Joined: 25 Aug 2008 |
| Total Posts: 4533 |
|
|
| 01 Sep 2011 04:53 PM |
> well technically their values can be nil
Lies:
local t = {} t["myKey"] = "myValue" for key, value in pairs(t) do print(key..": "..value) end -- prints "myKey: myValue" t["myKey"] = nil for key, value in pairs(t) do print(key, value) end -- prints "" t[nil] = "myValue" -- errors |
|
|
| Report Abuse |
|
|
|
| 01 Sep 2011 04:54 PM |
@NXTBoy
Keys and values can be absolutely any data type, except keys can't be nil. Other than that, there are no restrictions. |
|
|
| Report Abuse |
|
|
NXTBoy
|
  |
| Joined: 25 Aug 2008 |
| Total Posts: 4533 |
|
|
| 01 Sep 2011 04:55 PM |
Wait, misread as "keys and values".
The value does not become nil though. The key is removed from the table. |
|
|
| Report Abuse |
|
|
swmaniac
|
  |
| Joined: 28 Jun 2008 |
| Total Posts: 15773 |
|
|
| 01 Sep 2011 05:00 PM |
@NXT
To a normal scripter, the difference is not apparent. |
|
|
| Report Abuse |
|
|
NXTBoy
|
  |
| Joined: 25 Aug 2008 |
| Total Posts: 4533 |
|
|
| 01 Sep 2011 05:02 PM |
| @swmaniac: "Technically" does not mean "To a normal scripter" |
|
|
| Report Abuse |
|
|
swmaniac
|
  |
| Joined: 28 Jun 2008 |
| Total Posts: 15773 |
|
|
| 01 Sep 2011 05:04 PM |
Technically (omitted phrase: to a normal scripter)
In this context means:
It is possible to do (omitted word: apparently), but may cause problems. |
|
|
| Report Abuse |
|
|
NXTBoy
|
  |
| Joined: 25 Aug 2008 |
| Total Posts: 4533 |
|
|
| 01 Sep 2011 05:10 PM |
According to my dictionary, Technically means:
According to the facts or **exact** meaning of something.
The exact meaning does not change whoever the concept is being explained to. Therefore, "technically to [person]" means the same for all values of "person" |
|
|
| Report Abuse |
|
|
swmaniac
|
  |
| Joined: 28 Jun 2008 |
| Total Posts: 15773 |
|
|
| 01 Sep 2011 05:16 PM |
Oh my, I seem to have used the common definition of the word rather than the dictionary definition. What a horrible crime.
Also: I seem to have misled a fellow scripter by telling him an easier way to remember some trivia rather than what that trivia actually is, when in fact the issue should not come up at all and would in fact be of no difference to any practical use on Roblox. |
|
|
| Report Abuse |
|
|