TOPIC:

Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

Hi all,

Please find Elvior’s answer below.

We will also rise CR on this matter.

BR,
Andrus Lehtmets
Elvior

From: Tomas Urban
Sent: Wednesday, July 04, 2012 10:34 AM
To: Andrus Lehtmets (Elvior)
Subject: Re: Fw: referencing record of elements


First of all, all those assignments are invalid for a simple reason. The "vroi" variable is not a template variable, so it is not allowed to assign matching symbols to it.

If that the variable "vroi" were declared correctly as a template variable:

1. The first example would be correct. There's no rule forbidding overwriting of individual record of elements with a new value.
2. The 2nd and 3rd example should produce the same result. However, I am afraid that ES 201873-1 4.4.1 doesn't give a good guidelines for this situation. There is no rule in 15.6.3 (or anywhere else) saying that a mechanism similar to the one described in the paragraph 15.6.3.b shall be applied to record of values containing AnyElementsOrNone as the last element. However, you can find application of this non-existent rule in the example section. So there's definitely a problem with the specification. I will submit a CR regarding this issue.
Anyway, the result would be either:
Assuming that there's no rule regarding terminating AnyElementsOrNone, the element should be simply appended to the original template (using rules from the chapter 6.2.3): { ?, 2, *, 4 }
Using the same mechanisms as in the examples from the chapter 15.6.3.b: { ?, 2, ?, 4, *}

Our tool uses the latter approach.

--Tom

Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

Hello,

we agree in general with the assessment of Elvior.
The standard maybe is not explicit enough, although implicitly, the rule
15.6.3. b) is clear as always the relation

? =^= {*} for record of/set of templates is true.

The example which assigns a matching mechanism to an element which is
covered by an * (AnyElementsOrNone) confirms this interpretation.

Therefore, we at Testing Tech do not think it really necessary to change
the standard, but as long as the interpretation given also by Elvior is
maintained, we will support a CR in that regard.

BR, Jacob Wieland

Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

Sorry for the inconvenience, but I had problems with the time keeping
of my machine. According to this I sent the message back in July 2004.
Now I re-send it with the proper timestamp.

BR.,
Uwe

Hello Uwe,

I would expect t_RoI[5] to be 2 in both cases.

BR, Jacob Wieland

Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

Hello Uwe,

No, * in a record of is not a single element but represents an arbitrary number (from zero to infinity) of elements.

{*} is semantically equivalent to ({}, {?}, {?,?}, ...) (and {x, y, z, *, a, b, c} is equivalent to { x, y, z } & {*} & { a, b, c})

Thefore, the indices of elements following a * are undetermined (which is why they can never be accessed). If the star is length-restricted with a fixed length however, this changes.Then it is equivalent with the same number of ? as in the length restriction and the following elements again have fixed indices.

A permutation construction is pretty much the same as a special *, so the same rules apply to elements after it.

So, no, I would not say that the matching capabilities of * should be ignored when accessing the element-templates.

BR, Jacob Wieland

Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

Hi,

We also agree. In case of example 1, Currently there is no rule how to calculate the position of elements following AnyElementOrNone at assignments. So, the task here is to define this rule.
The rules used for examples 2 and 3 should explicitly be defined as mandatory rules in the text.

BR, Gyorgy

Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.