Range checking on config file
Hal Murray
hmurray at megapathdsl.net
Tue Jan 2 09:59:01 UTC 2018
Unless I missed something, the code processing gonfig slots can't distinguish
-1 from 0xffffffff or the equivalent decimal number.
They both come through as T_Integer. There is no T_Unsigned
The checking code gets to pull it as either xx->val.i or xx->val.u
struct attr_val_tag {
attr_val * link;
int attr;
int type; /* T_String, T_Integer, ... */
union val {
int i;
unsigned int u;
int_range r;
double d;
char * s;
} value;
};
--
These are my opinions. I hate spam.
More information about the devel
mailing list