> And its method of 
> representing arrays allow you to *literally* drop complex data 
> structures in to the array, for immediate use. For example, in the 
> client I use it in, if you want to get data on something as simple as a 
> line of text, you need to just push the data into a table in Lua, then 
> access it like an array. The method for transferring such data "into" 
> Lua is fairly trivial. Other languages *can't* handle the transfer of 
> such structured data. They are forced to rely on creating multiple 
> arrays, to hold each subtype of data. So while Lua uses a single table 
> that looks like:
> 
> mytable (position)
>   \---Letter
>   \---Font
>   \---Color
>   \---Ect.
> 
> In *any* other language you need to do something like:
> 
> dim letter()
> dim font()
> dim color()
> dim etc()
> 
> Then load **each** of those independently.

Umm... Isn't that how things work on *any* loosely-typed language?

var arr = [123, [12,34], "foo", /\s+public ?(.*)/g, new Sphere(1,2,3)];

A valid Javascript array containing a number, another array, a string, a 
regular expression, and a Sphere (provided that the Sphere object was 
defined).

Post a reply to this message