thomas169 commented on pull request #233:
URL: https://github.com/apache/plc4x/pull/233#issuecomment-827089647
its done in relation to the title. But any commits to my fork also come into
this PR, hence the later 3 commits.
--
This is an automated message from the Apache Git Service.
To
sruehl edited a comment on pull request #233:
URL: https://github.com/apache/plc4x/pull/233#issuecomment-826740945
out of curiosity: as you (@thomas169) marked it for ready for review and
added changes to it 7 days after: is it done done yet? If so maybe I would
suggest that @ottobackwards
sruehl commented on pull request #233:
URL: https://github.com/apache/plc4x/pull/233#issuecomment-826740945
out of curiosity: as you marked it for ready for review and added changes to
it 7 days after: is it done done yet? If so maybe I would suggest that
@ottobackwards or @chrisdutz shoul
Noticing int the last mail that the rendering is completely broken here again
the old mail as plain text:
Last week I did some progress on plc4go that I want to summarize with this mail:
1. big.Int & big.Float Support:
a. Like in Java we can now support oversized ints and
Somehow the mailing list removed all the bullet points (apparently it doesn’t
like html mails). Here again hopefully readable as plain text:
TLDR: changes in plc4x which help developing drivers across languages that have
no effect how plc4x send/receiver data or how you use the API
As of the la
Hi Sebastian,
thanks for this summary and thanks for your hard work on all of that in the
last few weeks. Looking forward to profiting from these changes (Currently I'm
stuck with other things in my working time and in my private time I'm working
hard on getting my I40 factory working)
Chris
TLDR: changes in plc4x which help developing drivers across languages that have
no effect how plc4x send/receiver data or how you use the API
As of the last mail `Progress on plc4go` from 15.03.2021 I want to give another
overview what has happened between 1bd132a to f97d36f
Changes on read/wri
