Actions
Bug #3008
closedprint big fat error message in case somebody registers osmo_fsm without event names
Start date:
02/26/2018
Due date:
% Done:
0%
Spec Reference:
Description
Ideally I would want to reject registrations without event names, but it seems that multiple of those have already been slipped into our codebase :(
So let's add a big fat warning that this is improper API use and that it will eventually be enforced.
Related issues
Updated by laforge about 6 years ago
- Related to Bug #3007: make sure all libosmocore code can tolerate FSMs without event names added
Updated by stsp about 6 years ago
- Status changed from New to In Progress
Proposed patch in https://gerrit.osmocom.org/6951
Updated by stsp about 6 years ago
- Status changed from In Progress to Resolved
Above change has been merged.
Actions