Re: [C++] developers -- how you watch Unicode strings in debugger?
Re: [C++] developers -- how you watch Unicode strings in debugger?
- Subject: Re: [C++] developers -- how you watch Unicode strings in debugger?
- From: Sebastien Metrot <email@hidden>
- Date: Fri, 13 Apr 2012 02:24:14 +0200
Ruslan,
Sorry for not being helpful. I agree that Xcode should support this but after having waited for this to happen for years I finally took the only realistic and possible decision. In the end it was also a good decision for the target binaries on mobile platforms memory-wise, so I don't regret it.
S.
--
Sebastien Metrot
Yasound - CTO - Cofounder
email@hidden
On Apr 13, 2012, at 12:45 AM, Ruslan Zasukhin wrote:
> Hi Sebastien,
> Hi Dmitry,
>
> I am 10 years users of xcode, and frankly saying both your answers are not
> much helpful to me :-( May be I need re-read this at morning tomorrow :)
>
>
> I really do not understand, what technical troubles exists to show us UTF-16
> string right in the place where we see variables.
>
> z (int) 5
> p (char*) "abcd"
> p2 (whcar_t*) "abcd" 4-bytes chars, UTF-32
> p3 (ushort*) "abcd" 2 bytes chars, UTF-16
>
> ??
>
> Text files can be encoded UTF8, UTF16 and UTF32.
> XCODE perfectly is able show us this in editor.
>
> What problems show us these strings in debugger?
>
> Than more that LLVM has "View Variable as UTF16",
> But instead of string it show numbers:
> "05 06" "24 06"
>
> Why not just "CD"?
>
> MS Visual C++ do this perfectly. For years ...
> So there is no technical problems ...
> WE must get this just from box. Automatically.
>
> XCODE itself show us these chars in the MEMORY Browser.
> Why not in place for variables?
>
> Why everybody from us should define "GDB custom method" ?
>
>
> On 4/13/12 12:27 AM, "Dmitry Markman" <email@hidden> wrote:
>
>> define gdb custom method, that will use some
>> API that you should create
>>
>> that API will convert wchar_t to UTF8 and then just use gdb's print
>> it should work, because mac os x terminal understands utf8
>> hope it will help
>
>
> and
>
>> On 4/13/12 1:28 AM, "Sebastien Metrot" <email@hidden> wrote:
>
>> This problem was one of the reasons for moving all my code base from wchar_t*
>> to char* (and utf8). If your code really is unicode aware you will have to
>> handle many special cases where one codepoint!=one glyph/entity anyway
>> (diacritics, normalization, etc). Enumerating unicode code points in an utf8
>> string is easy to implement and it forces you to really think about semantics
>> of what you want to do with the text.
>> And it displays nicely in the debugger, even as an std::string ;-).
>>
>> S.
>>
>>
>> --
>> Sebastien Metrot
>> Yasound - CTO - Cofounder
>> email@hidden
>>
>>
>>
>>
>> On Apr 12, 2012, at 10:03 PM, Ruslan Zasukhin wrote:
>>
>>> Hi C++ developers,
>>>
>>> Using 4.3.2 XCODE and even LLVM debugger
>>> We still was disappointed that debugger is not able show unicode strings.
>>>
>>> Actually even std::strings (wchar_t*) are not shown ...
>>>
>>> We need each time open memory browser to see Letters ...
>>>
>>>
>>> Any hint?
>>>
>>> How to live without this? :-)
>
> --
> Best regards,
>
> Ruslan Zasukhin
> VP Engineering and New Technology
> Paradigma Software, Inc
>
> Valentina - Joining Worlds of Information
> http://www.paradigmasoft.com
>
> [I feel the need: the need for speed]
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden