qleisan
qleisan
@sbertin-telular you made a clarifying comment, thanks. Can you elaborate a bit more? Does this require a programming error e.g. on the implementation of the `targetP->readFunc` for a not yet...
@stefanfangvall @sbernard31 Do we know a specific function/scenario that can cause pointer misuse? If not, I think this issue can be closed and the coding style discussed in https://github.com/eclipse/wakaama/issues/513#issuecomment-763513438
I agree. Tests also help to clarify what is supported (partially or fully).
@sbernard31, @rettichschnidi - shouldn't the demo examples be robust enough to handle a situation like this or will that lead to much more complicated examples? Maybe a list of improvements...
Yes definitely. The discussion should also cover how to interact more easily with objects on the client side from the "application".
In PR #461 the "test_block1_retransmit()" is disabled. The test is considered faulty not the code. Should be revisited and re-enabled
Decide coding style for when to check pointers https://github.com/eclipse/wakaama/issues/514#issuecomment-761041820 https://github.com/eclipse/wakaama/issues/506#issue-752058734 "always check for runtime errors but not always for programming errors...". This needs to be refined but IMHO it doesn't...
Joining the reboot
[Cybercom](https://www.cybercom.com/) has identified Wakaama as a project of interest for our IoT business/consultancy
@sbertin-telular any thoughts on the way forward for this issue? Would like to reduce the number of open bugs...