Julius Pfrommer
Julius Pfrommer
@RolfKal, We have thought about your use case. And how we can get a generalized solution that works across different services. Please check if the following works for your use...
Cool. We will verify against the foundations CTT tools…
The array needs to be prefixed with a size_t length field in the struct. See /examples/custom_datatype/custom_datatype.h --> `struct Measurements`.
The goal of this PR is good. The change is however quite fundamental. We should do it step-by-step. And avoid breaking of existing code that uses the library. 1) Correcting...
The first member of String and ByteString is a size_t. There is no padding after size_t because it has the word size of the processor architecture. So the layout of...
The structure definition is wrapped in “extern C” so any c++ compiler knows how to do the member alignment. I know the notion of “plain old data” POD structs has...
Thanks. Please accept the CLA and have a Look at the red CI Runs.
Which version of the library? Please show server logs to get more insight.
Yeah. I think we can remove UA_BYTESTRING entirely. It is much butter to use `UA_ByteString_fromBase64`. Or to initialize the structure directly as `UA_ByteString b = {len, buf};`.
What about the raw encoding? What about DataValue with the timestamp not included?