ros2/openvehicle-api
3
0
Fork 0
mirror of https://github.com/eclipse-openvehicle-api/openvehicle-api.git synced 2026-02-05 15:18:45 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

Precommit (#1)

Browse Source 
* first commit

* cleanup
This commit is contained in:
tompzf
2025-11-04 13:28:06 +01:00
committed by GitHub
parent dba45dc636
commit 6ed4b1534e
898 changed files with 256340 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
open_points_framework.txt Normal file
View File

@@ -0,0 +1,11 @@
The following issues need to be solved:
- The proxy and the stub need access to the local core services (local for the exe they are running in), for:
- Memory allocation / release
- Interface marshalling
--> In case the component allocates data to return (e.g. strings, vectory, maps), the stub will NOT free this memory,
but the memory has to be freed by the caller of the "Call" function (e.g. the receiver of the IPC communication).
This can be identified by the interpretation of a parameter being "indirect" for "ret", "out" and "inout" parameters.
--> In case the component parameters do not fit in 8 bytes, the stub will allocate memory, which needs to be released
by the caller of the "Call" function (e.g. the receiver of the IPC communication). This can be identified by the
interpretation of a parameter being "indirect" for "ret", "out" and "inout" parameters.