Eliminate kernel object API anomalies #2423
Labels
area: Kernel
Enhancement
Changes/Updates/Additions to existing features
priority: high
High impact/importance bug
Milestone
Reported by Benjamin Walsh:
Most of this is already done, but keep for reference until this list is gone through with a fine comb:
A potpourri of API inconsistencies that should be fixed:
** These still exist for mutex and thread types.
** These still exist for mutex and memory pool.
** May also want to get rid of for timer?
** May also want to get rid of for thread? (I think Ben has a good argument for keeping this one, but I'm not sure ...)
** Currently can specify delay via k_thread_spawn() only ...
** In some cases you may need to change the code -- in other cases you may need to change the documentation.
** Should review all kernel object types, but at one point there were issues with thread, memory map, stack, message queue, and pipe.
** Issues to watch for:
*** Missing arguments; extra arguments; arguments in the wrong order.
*** Should try to have consistency when specifying "related" arguments. One thing in particular to try and ensure is that whenever an object is passed a pointer to a memory region and a size for that region, the pointer should be first and the size (or, in some cases, sizes) should be second. Right now we seem to have cases where the pointer comes last ...
(Imported from Jira ZEP-916)
The text was updated successfully, but these errors were encountered: