thebreaker

I meant the newest version of the script of course. The downloadable AutoIt version (installer) is dated from before the change was made and does not contain it I believe. It doesn't make sense if we talk here about a changed version of an include file and I can't download the current development version from somewhere... Sad that Autoit source is not available anymore publicly. I assume one must pay for it some day and I can now look for an alternative.

Where can I find the source code of AutoIt (and the changed array.au3)? I couldn't find a link on the homepage.

This is not only about my personal expectation. I could use the old version of the module and everything works as before. The question is what the general expectations from users/programmers using functions are and what your (or the AutoIt projects') standards / guidelines are to define functions and modules. I think my expectation would be common sense between programmers and program language / API designers. If this is the case, the function should IMHO be changed (again). The absence of objections is not necessarily the best basis for a decision - I don't know how many think about such things or follow these threads. Of course, the decision is yours. I just want to make sure my point is understood correctly.

I couldn't find the time to test the new function in the setting at work with big data arrays. Maybe I can test it tomorrow. What I'm not sure about is why an _ArrayAdd function should split a string parameter and add single parts by default. If I have a function "Add(a, b )", a user IMHO would intuitively think that "b" is added, and not transformed into other elements which then would be added. That's not intuitive. I would suggest, that the function behaves the other way around, that is: add the parameter/object unchanged by default, and do something tricky if the user gives additional parameters to do so.

I have a serious problem with the _ArrayAdd function as well: I already read that the syntax changed, and although it means I have to change my scripts, I can live with that. But I can't make the new function support what I need: What I currently use as functionality from the "old" version of _ArrayAdd is to store whole arrays as objects in an array. My use case is that I read many files (with _FileReadToArray) which I use later on. To avoid that the files have to be read multiple times, I store them in an array with _ArrayAdd($dataArray, $myFileContentArray). The problem is that the new _ArrayAdd function detects that the object I want to add is an array, splits it up and adds the single elements (lines). That's not what I want. How can I have the old behavior (storing the whole "file content array" as one element)? I read that the new _ArrayAdd has this $hDataType parameter. Is there a possible value I could use to make the new _ArrayAdd store the complete array as with the old _ArrayAdd function? I did not find something in the documentation.