2 Dec
2016
2 Dec
'16
1:48 p.m.
On Fri, Dec 02, 2016 at 01:43:40PM +0100, Neels Hofmeyr wrote:
I would rather have code that doesn't have such assumptions in the
firstp place, without relying on the fact that an enum of a library
doesn't extend in the future.
I see the assert more as a hack around code with broken assumption.
From that
point of view, the static_assert is highly questionable in
openbsc.git
I'm glad that we have the assert, otherwise we would be writing past the
array's end without noticing now... What did you have in mind?
I don't have the time right now to study the particular code in
question, sorry. It will hav to wait for another 10 or 20 other things
on my ever growing stack of todo items :/
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)