Skip to content

Conversation

@ranft
Copy link

@ranft ranft commented Apr 27, 2016

The modbus_reply-function was changed to support callbacks instead of a memory mapping. The memory mapping is now a specialized case of the callback mechanism, in order to handle both cases the same way (= no copies of existing code).

@karlp
Copy link
Contributor

karlp commented Apr 28, 2016

I like the general idea of this (a lot) but haven't tried this out yet.

The application now does get a notification after the read or write is done.
Also the reason for the buffer retreival is now visible to the application.
modbus-tcp-private.h \
modbus-version.h
modbus-version.h \
virtual-reply.c
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indentation + name...

@stephane
Copy link
Owner

I intend to apply a few changes on libmodbus (DRY in modbus_reply) and to review other work on callback feature before choosing the best way to add this feature. Stay tuned and thank you for your PR!

@stephane stephane added this to the v3.4.0 milestone May 18, 2016
@stephane stephane self-assigned this May 18, 2016
@stephane
Copy link
Owner

stephane commented May 20, 2016

@ranft I'm sure you'll be interested by the recent changes I applied to libmodbus master few hours ago ;)

73a88a7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants