Template Initial Value and Dictionary

, ,
1

Imported from previous forum

2

Newbie question:

Does anyone know where I can find a clear explanaiton regarding a fields initial state (reset state) in the dictionary depending on if there is an initial value specified in the template or not? For example: If a copy operator has no initial value, is the dictionary state set to undefined vs assinged with a previous value equal to the inital value if one is specified.

Thanks in advance,
Mike

3

Mike,

pls read section 6.3 of the specification. Section 6.3.5 covers your example. Let us know if you have any more specific questions regarding the spec language.

Best,
Rolf

Newbie question:

Does anyone know where I can find a clear explanaiton regarding a fields
initial state (reset state) in the dictionary depending on if there is
an initial value specified in the template or not? For example: If a
copy operator has no initial value, is the dictionary state set to
undefined vs assinged with a previous value equal to the inital value if
one is specified.

Thanks in advance, Mike

4

Thanks for your prompt reply. I read that section and took it to mean that for a dictionary reset, or a new UDP packet arrival, the state of each field in the dictionary should be set to UNDEFINED even though initial values are specified in the template? I was getting mixed messages after reading a number of posts on the forum.

Mike

Mike,

pls read section 6.3 of the specification. Section 6.3.5 covers your
example. Let us know if you have any more specific questions regarding
the spec language.

Best, Rolf

Newbie question:

Does anyone know where I can find a clear explanaiton regarding a
fields initial state (reset state) in the dictionary depending on if
there is an initial value specified in the template or not? For
example: If a copy operator has no initial value, is the dictionary
state set to undefined vs assinged with a previous value equal to the
inital value if one is specified.

Thanks in advance, Mike

5

Mike,

yes, that’s correct.

Section 6.3 states:
“All values are in the state undefined when processing starts.” and
“A dictionary can be explicitly reset. Resetting a dictionary will set the state of all its entries to undefined.”

Regarding a field with a copy operator, section 6.3.5 states:
"When the value is not present in the stream there are three cases depending on the state of the previous value:
…

  • undefined – the value of the field is the initial value that also becomes the new previous value.
    …"

/Rolf

Thanks for your prompt reply. I read that section and took it to mean
that for a dictionary reset, or a new UDP packet arrival, the state of
each field in the dictionary should be set to UNDEFINED even though
initial values are specified in the template? I was getting mixed
messages after reading a number of posts on the forum.

Mike