man, these samples are pretty long to go with, but from overall issue it
seems like we need to do reflect multi layer protocols in a better way.
As far I understand the problem - it boils down to underlying buffer
which is started with BE and we need to read things using LE.
I see issue in two
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [638]':
Is back to normal.
Bringing the thought of the other discussion here too ...
How about adding name-value paris to the type declarations as well as to the
fields? Then the "try" flag could be replaced with a name-value pair or even a
name=expression pair ... sort of like "parse-behaviour=try" or something
similar
Hi all,
I'm currently working on the PROFINET ... here I have the challenge, that I
have multiple layers of different protocols.
UDP -> DCE/RPC -> PROFINET IO CM (Block Container) -> PROFINET IO CM Blocks
The problem is:
* UDP is Big Endian
* PROFINET IO CM Blocks are Big Endian
*
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [637]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/637/";>PLC4X/PLC4X/develop
[develop] [637]"
Hey Lukaz,
the optional after the try is just a coincidence from the bac spec. Like it say
the low should always appear with a high and if the id is set then no name
should not be set. But in itself the try is self sufficient and behaves indeed
like an optional without an expression. Other than
Hmm ... you actually bring up a good point here Lukasz.
In the end doesn't the "try" flag simply make it an optional with a different
type of optionality condition?
Cause right now there are differences between optional and simple types in the
way the references are stored.
For example a "uint 8
