Search found 2771 matches
- 08 Aug 2023 11:18
- Forum: Bug Reports
- Topic: [solved] Problems with dereferenced access to array-elements
- Replies: 12
- Views: 433
Re: Problems with dereferenced access to array-elements
Thanks for the good explanation :appl: Still I don't know why the function sees the array (this is a must), while the step dialog doesn't. I'd say it's important that it's an array, and only "by the way" it also has a 'base' var. For me it's "not expected". But I can live with th...
- 07 Aug 2023 23:11
- Forum: Bug Reports
- Topic: [solved] array-elements in quotes not resolved
- Replies: 3
- Views: 211
[solved] array-elements in quotes not resolved
Please say multiple "Oh no!" - I did. So exec the included script, as is, and note the comments. (Problem only on elements with index = characters) You remember my un-answered questions about adding associate elements to an indexed array? You and I would not have thought of this answer, so...
- 07 Aug 2023 20:07
- Forum: Bug Reports
- Topic: [solved] Problems with dereferenced access to array-elements
- Replies: 12
- Views: 433
Re: Problems with dereferenced access to array-elements
OK: I misunderstood that the function definition should specify the []. (So I wrote that the function doesn't know it before being called.) But it's the parm in the call . That relaxes a lot. But if $a is non-array, and $a[] is array, it's strange that the function sees vartype($p3) as 'array' if ca...
- 07 Aug 2023 15:58
- Forum: Bug Reports
- Topic: [solved] Problems with dereferenced access to array-elements
- Replies: 12
- Views: 433
Re: Problems with dereferenced access to array-elements
Isn't this a bit of syntax mismatch :?: For explode() + implode() the array variable is defined to *not* have [] For array() it defines that both is allowed And now you say there's a difference between $a and $a[]. :shock: Problem for me: *the caller* decides, if a parm is string or array - the scri...
- 07 Aug 2023 13:29
- Forum: Bug Reports
- Topic: [solved] Problems with dereferenced access to array-elements
- Replies: 12
- Views: 433
Re: Problems with dereferenced access to array-elements
First *test* shows: this problem is solved! Before trying in productive script: Report a follow-up problem! (It was there before your change - I didn't want to mix it up :whistle: ) See following example-script: if executed in stepping mode, the call to f() will only report 3 parms - the 4th is tota...
- 07 Aug 2023 11:58
- Forum: Bug Reports
- Topic: [solved] Problems with dereferenced access to array-elements
- Replies: 12
- Views: 433
Re: Problems with dereferenced access to array-elements
If I interpret it right it is exact what I meant = wanted!
OK: when you're ready with *everything* else, you could add the logic with ()
edit: typo
OK: when you're ready with *everything* else, you could add the logic with ()
edit: typo
- 07 Aug 2023 11:36
- Forum: Bug Reports
- Topic: [solved] Problems with dereferenced access to array-elements
- Replies: 12
- Views: 433
Re: Problems with dereferenced access to array-elements
Fortunatually you're going to fix it
Waiting ... can't get on till then.
Bad that I'm always doing things for the first time
Waiting ... can't get on till then.
Bad that I'm always doing things for the first time
- 07 Aug 2023 00:21
- Forum: Bug Reports
- Topic: [solved] Problems with dereferenced access to array-elements
- Replies: 12
- Views: 433
[solved] Problems with dereferenced access to array-elements
OK: short version. Assume: $p contains the variable-name '$A3' of an array. For both: $ele2 = *$p[2]; // copy 1 element of array *$p[2] = 'X2'; // set 1 element of array *$p[2] could be interpreted 2 ways, I demonstrate them with (): (*$p)[2] or *($p[2]) I'd expect (and wish) the first version - as ...
- 04 Aug 2023 17:19
- Forum: Bug Reports
- Topic: ForEach on array with dereferenced variable
- Replies: 4
- Views: 230
Re: ForEach on array with dereferenced variable
Now it's later. (Much!)
After fixing my own ( )
I could verify: this is fixed, too!
So thanks again!
After fixing my own ( )
I could verify: this is fixed, too!
So thanks again!
- 04 Aug 2023 12:21
- Forum: Wishes
- Topic: InputSelect(), pre-select one line
- Replies: 4
- Views: 313
Re: InputSelect(), pre-select one line
But at least a circumvention, i.e. get the (variable) full line, is possible.
(Though not nice.)
- 04 Aug 2023 12:15
- Forum: Bug Reports
- Topic: ForEach on array with dereferenced variable
- Replies: 4
- Views: 230
- 03 Aug 2023 16:01
- Forum: Bug Reports
- Topic: ForEach on array with dereferenced variable
- Replies: 4
- Views: 230
Re: ForEach on array with dereferenced variable
Trying to circumvent the problem I tried to copy the (real) array before ForEach(): $p4 = an array like before $var = '$p4'; $value = *$var; // ERROR: this assigns "" to $value As before I tested a string instead of an array: no problem! So dereference to a variable that's an array seems t...
- 03 Aug 2023 11:53
- Forum: Wishes
- Topic: InputSelect(), pre-select one line
- Replies: 4
- Views: 313
Re: InputSelect(), pre-select one line
Don, did you miss this wish
- 03 Aug 2023 11:51
- Forum: Bug Reports
- Topic: ForEach on array with dereferenced variable
- Replies: 4
- Views: 230
ForEach on array with dereferenced variable
ForEach($tok, *$var) (i.e. for a string) works OK ForEach(*$var, ...) (i.e. for a dereferenced array) leads to ERROR 9 | Subscript out of range. I'm convinced the second should work - especially as the first does? Example, for string and for array: //§ Test ForEach with DeReference "Test ForEac...
- 26 Jul 2023 11:47
- Forum: Bug Reports
- Topic: Website and Help Typos
- Replies: 392
- Views: 95475
Re: Website and Help Typos
My misunderstanding? 25.7. 9:37 you reported new beta AND new help file. so about noon I downloaded the help-pdf. 25.7. 20:00 you reported the full version - then I downloaded that, too. Seems the pdf was ready only after the info about full version? Then * Updated the help file. might be a bit misl...