Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Missing type specification from iotSocketGetOpt and iotSocketSetOpt #8

Open
paul-szczepanek-arm opened this issue May 9, 2022 · 1 comment
Open

Missing type specification from iotSocketGetOpt and iotSocketSetOpt #8

paul-szczepanek-arm opened this issue May 9, 2022 · 1 comment

Comments

@paul-szczepanek-arm
Copy link
Contributor

paul-szczepanek-arm commented May 9, 2022 •
edited
Loading

Options should have platform specific independent type and size (like uint32_t) that is checked against. Right now the implementations pass through the type instead of translating between implementation and API. This means the user needs to know the implementation detail instead of relying on the API.
See: #7

I propose we list all options with corresponding sizes in the doxygen block of the function.
@paul-szczepanek-arm paul-szczepanek-arm mentioned this issue May 9, 2022
Open
RobertRostohar added a commit that referenced this issue Jul 8, 2022
@RobertRostohar
Add type specification for socket options (#8)
927626f
@RobertRostohar
Copy link
Contributor

Type specification has been added to the documentation as requested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@RobertRostohar @paul-szczepanek-arm