Hi Mike,
I have started on a spec which I planned to use for building both a testsuite
for the code generation as well as for documentation purposes:
plc4x/build-utils/protocol-test/src/main/resources/protocols/test/test.mspec
It’s not complete and not a real protocol, but I think it should
Chris,
Thanks for this. Very useful. When I look at that ASN.1 ECN definition I have
the same reaction to it that I'm sure many non-XML people have to XML Schema
and DFDL, which is there is much to learn, and so little of it seems relevant
to the immediate problem. As soon as a description
Hi all,
+1 (binding)
I checked:
- Checked out using tooling
- Checked Signatures and Hashes
- Checked README, RELEASE_NOTES, LICENSE and NOTICE
- Checked README and RELEASE_NOTES are same as in the zip
- No unexpected binaries
- Builts on my MAC according to documentation in README (`mvn clean
Christofer Dutz created PLC4X-149:
-
Summary: Move the Python, C++ and C# drivers into the sandbox
Key: PLC4X-149
URL: https://issues.apache.org/jira/browse/PLC4X-149
Project: Apache PLC4X
Christofer Dutz created PLC4X-148:
-
Summary: Update the build to allow reproducible builds
Key: PLC4X-148
URL: https://issues.apache.org/jira/browse/PLC4X-148
Project: Apache PLC4X
Issue
