You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Applications that choose pointer callbacks throughout a build may want to use the familiar tx_thread_create and tx_timer_create names. The additive APIs proposed in #771 provide this behavior per call; #413 documents why changing the existing signatures by default is disruptive.
I propose evaluating an optional source-level mode that maps those names to the new pointer APIs. It would use the same kernel implementation and ABI as the additive APIs, leave ULONG at 32 bits, and require matching callback signatures. I want the design to identify which existing callers, including component code that explicitly casts pointers to ULONG, would need edits or diagnostics.
I would leave delivery timing TBD. We should decide whether the naming convenience justifies a build-wide source contract after the additive APIs and a migration example are available.
Activity
Added opt-in pointer callback mode and creation APIs (eclipse-threadx…
Added opt-in pointer callback mode and pointer creation APIs (eclipse…