On 06/18/14 07:32, Paul Fertser wrote:
> Hi,
>
> On Wed, Jun 18, 2014 at 07:10:42AM -0700, Ram Bhamidipaty wrote:
>> The default build on my system (arch linux) builds jim tcl with utf-8
>> support.
>> This makes it hard to manipulate 8 bit data via tcl. Does OpenOCD need utf-8?
>> Will it be simple to turn off utf-8?
> Can you please clarify why exactly you do not like JimTCL built with
> utf-8? I've manipulated raw binary data just fine with it, what
> exactly is the issue? And it's a standard enconding nowadays anyway.
>
Sure - I have Tcl code that is trying to build some test data - a 256
byte string 0x00 .. 0xff.
This simple approach:
set data ""
for {set i 0} {$i < 256} {incr i} {
set data [format "%s%c" $data $i]
}
Does not work. For byte values above 0x7f I end up with something like
0xc2 0x80 etc. I guess
thats the UTF-8 stuff.
There is also trouble when trying to manipulate "character" values above
0x7f.
Is there a better way?
-Ram
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
