Oh yes - especally in an operating system/environment that is fundamentally event driven and busy-wait loops are not only frowned upon, but impossible to do without tripping the watchdog timer. (As they should do!).
Still, being able to restart a timer still wouldn’t solve my immediate problem, as I may never hit the timer handler if the comms is closed before a timeout occurs and the timer is manually unsubscribed.
Handling the context memory in the same fashion as memory in wm_lst() is (i.e. default to using adl_memRelease(), or user override with user defined function at list creation time) would be ideal.
Bump: Wavecom - please add this to the list of ‘TODO’ for upcoming versions of openAT.