> I needed a conversion from hex-string to integer and found
> this mail from Linus suggesting sscanf:
> but sscanf in linux-2.5/lib/vsprintf.c interpretes length attributes
> only when the type is a string. It uses simple_strtoul() and it will
> read the buffer until it finds a non-(hex)digit.
> int i;
> char str ="34AFFE45XYZ";
> sscanf(str, "%1x", &i);
> i will be '0x34AFFE45' instead of the expected '3'.
> Is this behaviour intended or is just nobody caring about?
The in-kernel vsprintf() is very primative, used for very simple
things. Note that it doesn't even have "%f". You should just
do something like:
i = (int) *str + '0';
... if you need to read part of a number.
You don't really wany to increase the size of the permanent
in-kernel stuff if you can help. You add any increased functionality
to your modules so it is used only when needed.
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/