J
Hello,
I've split up smm/smm_lib.c because it had two and a bit different ways of doing its stuff (and also it was over a thousand lines long).
There is no change to the API.
- smm_lib.c - now contains only the common stuff, and the initialization that decides which of the other two and a bit to use.
- smm_local.c - contains all the _local routines, which are used when the Shared Memory is to be accessed directly.
- smm_isolate.c - contains Mario's _isolate/_remote routines which are used
when the Shared Memory is to be accessed via proxy.
- smm_remote.c - contains the stub for having the proxy on a different machine.
I hope I haven't broken anything.
Jiri
--
Jiri Baum <[email protected]>
Windows is not popular. Windows is *widespread*. Linux is popular.
_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
I've split up smm/smm_lib.c because it had two and a bit different ways of doing its stuff (and also it was over a thousand lines long).
There is no change to the API.
- smm_lib.c - now contains only the common stuff, and the initialization that decides which of the other two and a bit to use.
- smm_local.c - contains all the _local routines, which are used when the Shared Memory is to be accessed directly.
- smm_isolate.c - contains Mario's _isolate/_remote routines which are used
when the Shared Memory is to be accessed via proxy.
- smm_remote.c - contains the stub for having the proxy on a different machine.
I hope I haven't broken anything.
Jiri
--
Jiri Baum <[email protected]>
Windows is not popular. Windows is *widespread*. Linux is popular.
_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc
