#2334 closed Bug (No Bug)
Maximum _useful_ array dimension is 24, not 64 as doc says
| Reported by: | jchd18 | Owned by: | |
|---|---|---|---|
| Milestone: | Component: | Documentation | |
| Version: | 3.3.9.4 | Severity: | None |
| Keywords: | Cc: |
Description
Barring using "dummy" dimensions like [1][1]... the maximum practical dimension of an array is 24, while the documentation says 64. Beyond 24D we hit "Array maximum size exceeded."
Local $arTestGood[2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2] Local $arTestUseless[1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1][1] Local $arTestBad[2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2][2]
Attachments (0)
Change History (3)
comment:1 by , 13 years ago
| Component: | AutoIt → Documentation |
|---|
comment:2 by , 13 years ago
| Resolution: | → No Bug |
|---|---|
| Status: | new → closed |
In fact there is no bug as it is not the number of dimension but the global size of the array which is reach 224
comment:3 by , 13 years ago
@JP,
That's what I said! And yes, it's not exactly a bug, rather an implementation error.
@Admiral,
This minor issue is both with the language and the documentation.
Building to a limit that is non-reachable in practice is at the very least questionnable. That the interpreter allows for a useless series of up to 64 [1] dimensions is pretty stupid: the practical limit (array size) is well below and if we start using [1] dummy dimensions, then why put a limit at all? And the doc should reflect that.
BTW, jchd18 = jchd and I've no problem with this ticket closed.

64 dimensions is a technical limit, nowhere does it say that it's a useful thing to do.
Besides, I'm not sure what you're asking us to do. Lowering the limit? What useful purpose could that possible have?