Re: Second call on encrypted connection

Holger Hans Peter Freyther wrote:

it should not happen (as the periodic LU timer should be stopped), but imagine the 'unsigned int' would be an 'enum', we would now have a warning about unhandled cases (e.g. not building a partition over the enum) and it is good practice to avoid it. there is a "default:", which will not cause any warning, since it handles all unhandled cases above. a.) If it can happen support it b.) If it can not happen, use LOGL_ERROR so we potentially notice if it does happen and then we can re-consider. LOGL_ERROR makes sense. maybe it tuns out that there is a call setup that caused a cell re-selection and a location updating is sent right afterwards.