On Saturday 23 January 2010, simon qian wrote:
>
> "TDI( 1234 )" should be OK.
> "TDI( 1 2 3 4 )" could even be parsed.
But (eventually)
PIOMAP (IN STROBE
IN ALE
OUT DISABLE
OUT ENABLE
OUT CLEAR
IN SET);
is going to require the spaces, right? (Example cut/paste
from the SVF spec.) So dropping spaces is odd...
I see that svf_copy_hexstring_to_binary() already has some
code to skip spaces ... isn't that behaving?
I looked at the SVF spec and it's kind of weak in terms of
basic lexical issues like where spaces are allowed or not.
Agreed that allowing whitespace in long hex strings makes
a lot of sense, especially if some tools generate them
(so there's a "de facto" requirement to allow them).
- Dave
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
