Idea for arrays

[Guest]

I think it is good idea to make this possible:

 

 

Such a an array allows you to hold information in a more convenient and efficient way.

Example:

This is a simple example. It does not have to be only TRUE / FALSE . it can be more of course.
 

Edited December 12, 2015 by Guest

[Melba23]

gil900,

And why do you see this as a good idea? Can you share a situation where it would be useful to have negative array indices?

M23

[Guest]

gil900,

And why do you see this as a good idea? Can you share a situation where it would be useful to have negative array indices?

M23

It is difficult for me at the moment to describe the situation in general and also explain arguments why it is good.
I will try to explain later

[Melba23]

gil900,

I will try and contain my impatience.....

M23

[guinness]

Build it yourself and don't rely on others to do it for you. The fact you can't come up with a use case, means this is just a feature for you only.

[Guest]

Suppose you have a main array.

And in that main array you need to store this kind of array:

 

In this array the the only information that can continue without end is Item X
 

Other information needs to be stored in array is regular information - information that needs only one slot such as: how many Items the array contains, variable that  represents a specific setting for all Items and more.

 

The problem is - you have one slot for it. In this it is the 0x0 slot. If I want to write in it more then one value directly (I want directly. don't want to create in it new array)
Then this is not possible.

 

Why I don't want to create new array in it?
If your code need to use some variable Intensively then you may want to save the process of loading /reading other array Every 10/5 ms just to read one value.

 

I will continue later

[iamtheky]

Can you describe that in code?  The wording is tough to decipher.

[Guest]

Can you describe that in code?  The wording is tough to decipher.

Which is why I did not try to start explaining before.. sorry.
It is much more the idea of organizing data more efficiently

 

Be patient. I'm working on a image that will show when it can be very useful (efficient data organization)..

[Melba23]

iamtheky,

As I understand it, the OP wants to have arrays that start at the [1] index with an unlimited number of prior indices ([0], [-1], [-2], etc) which can hold metadata such as the "count in [0]" so common in AutoIt arrays.

My response would be:

• Have as many such elements as you need and then start the array "proper" at the index which holds the first "data" rather then "metadata" - For...To...Next does not care which values you pass as limits and calculating "index - x" will not cost much.
• Use an array in the [0] element to hold all the metadata. You suggest that it would seriously slow the script - I would argue the contrary. Look at my GUIListViewEx UDF - there are many occasions where I set Local variables to the content of elements of an "array in array" so that there is not the repeated reading of these embedded values.

But let us wait to see what this promised image brings - perhaps I am completely wrong, and not for the first time!

M23

[Guest]

 I made this picture:

Hope this helps you understand the concept.

This opens up the possibility of creating a more complicated information and store it more efficiently. This example i have in my head of such data organization

 

Edited December 11, 2015 by Guest

[iamtheky]

just use a map, then you can call the indices whatever you want?

[JohnOne]

This opens up the possibility of creating a more complicated information and store it more efficiently. This example i have in my head of such data organization

This opens up the possibility of creating more complicated information and storing it more efficiently. This is an example I have in my head of such data organization.

[JohnOne]

just use a map, then you can call the indices whatever you want?

Good point, but with one minor problem. They're not in stable release

Edited December 11, 2015 by JohnOne

[iamtheky]

then fake it

 

[Guest]

just use a map, then you can call the indices whatever you want?

Can I store Map variable inside array?

[JohnOne]

The point would be to use a map instead of an array, you can store a map in a map.

Not sure about map in array.

Edited December 11, 2015 by JohnOne

[iamtheky]

definitely read the thread, if you start getting fancy and throwing dictionaries in the dictionary then the way I am retrieving data would have to be adjusted.  I would be happy to play along if you run into issues.

[Guest]

iamtheky,

As I understand it, the OP wants to have arrays that start at the [1] index with an unlimited number of prior indices ([0], [-1], [-2], etc) which can hold metadata such as the "count in [0]" so common in AutoIt arrays.

My response would be:

• Have as many such elements as you need and then start the array "proper" at the index which holds the first "data" rather then "metadata" - For...To...Next does not care which values you pass as limits and calculating "index - x" will not cost much.
• Use an array in the [0] element to hold all the metadata. You suggest that it would seriously slow the script - I would argue the contrary. Look at my GUIListViewEx UDF - there are many occasions where I set Local variables to the content of elements of an "array in array" so that there is not the repeated reading of these embedded values.

But let us wait to see what this promised image brings - perhaps I am completely wrong, and not for the first time!

M23

 

Have as many such elements as you need and then start the array "proper" at the index which holds the first "data" rather then "metadata" - For...To...Next does not care which values you pass as limits and calculating "index - x" will not cost much.

I hate to code this way.. it is mess. and I never did it
I don't want loop that start check from number that is > 1 just because I need to use the first indexes for the metadata (thanks for this word).
I see it wrong to write code like this even if it seems that it is the best option for the machine.

 

Use an array in the [0] element to hold all the metadata. You suggest that it would seriously slow the script - I would argue the contrary. Look at my GUIListViewEx UDF - there are many occasions where I set Local variables to the content of elements of an "array in array" so that there is not the repeated reading of these embedded values.

I didn't looked at it but I know what you did. you just  reducing the number of times of reading information from array in array..
But If you have array like I suggested then the "array in array"  requirement is reduced significantly and this is better. not only for performance but also (perhaps especially) for much cleaner code.

 

By the way,
I was wrong about the last picture I sent.
I should organize the data in this way:

 

This is how it may look with real data (Non-variable names)

This is simple example. It does not have to be only TRUE / FALSE . it can be more then that of course.

I added this image to the first post

 

 

 

 

Edited December 12, 2015 by Guest

[czardas]

Having negative array indices offers no advantage that I can see. What the images above are meant to demonstrate is also unclear. Looking at the code in the example I see... While Sleep(10). I don't like this loop syntax: . It is not a good idea to rely on the return value of a function which is documented as not having one. Using such a return value may seem clever, but it makes the code more difficult to understand.

Edited December 12, 2015 by czardas

[Guest]

Having negative array indices offers no advantage that I can see. What the images above are meant to demonstrate is also unclear. Looking at the code in the example I see... While Sleep(10). I don't like this loop syntax: . It is not a good idea to rely on the return value of a function which is documented as not having one. Using such a return value may seem clever, but it makes the code more difficult to understand.

Having negative array indices offers no advantage that I can see.

 

The ability to store more info such as count ("metadata") without the need to create more space in dimension 2 (Which it is expensive as long the array grows) or use indexes greater than 1 (Which is very uncomfortable to code loop that checking from index 4 for example)

You have almost unlimited space for "metadata" (such as count and more) and this space is cheaper ( In terms of performance & memory and convenience)

In terms of convenience:
You can have as many "metadata" in the array while still using For $i = 1 to $Array[0]  because most/all of it exists  behind the the 0.

In terms of performance  and memory:
You don't have to create new Array inside the Array just to store the "metadata". You saving the need of Extracting new array every time the code needs to reed some value.
In less words: This data is more accessible for the code. important thing when you want to get the maximum from Autoit.

 

 

Edited December 12, 2015 by Guest