Comments on: wchar_t: Unsafe at any size http://losingfight.com/blog/2006/07/28/wchar_t-unsafe-at-any-size/ i secretly code in visual basic Thu, 24 Dec 2009 13:45:24 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Heiko http://losingfight.com/blog/2006/07/28/wchar_t-unsafe-at-any-size/comment-page-1/#comment-31 Heiko Sat, 12 Apr 2008 07:29:41 +0000 http://www.losingfight.com/blog/2006/07/28/wchar_t-unsafe-at-any-size/#comment-31 Nice and sound wrap-up. Nice and sound wrap-up.

]]> By: ken http://losingfight.com/blog/2006/07/28/wchar_t-unsafe-at-any-size/comment-page-1/#comment-30 ken Fri, 15 Feb 2008 19:21:22 +0000 http://www.losingfight.com/blog/2006/07/28/wchar_t-unsafe-at-any-size/#comment-30 Nice. :-) FWIW, CFStringRef is open source and can be compiled for windows. It's part of CF Lite. Nice. :-)

FWIW, CFStringRef is open source and can be compiled for windows. It’s part of CF Lite.

]]> By: Slow Learner http://losingfight.com/blog/2006/07/28/wchar_t-unsafe-at-any-size/comment-page-1/#comment-29 Slow Learner Sat, 24 Nov 2007 04:02:17 +0000 http://www.losingfight.com/blog/2006/07/28/wchar_t-unsafe-at-any-size/#comment-29 Yet even more enjoyable. Apple's use of HFSUniStr255 is based on UniChar a UInt16 and is the only predictable way of navigating directories with their whacked up naming convention issues. Am I the only one that thinks Steve Jobs needs to stop playing with his iPhone and get back to work!!! Yet even more enjoyable. Apple’s use of HFSUniStr255 is based on UniChar a UInt16 and is the only predictable way of navigating directories with their whacked up naming convention issues. Am I the only one that thinks Steve Jobs needs to stop playing with his iPhone and get back to work!!!

]]> By: Robert http://losingfight.com/blog/2006/07/28/wchar_t-unsafe-at-any-size/comment-page-1/#comment-28 Robert Wed, 03 Jan 2007 01:09:02 +0000 http://www.losingfight.com/blog/2006/07/28/wchar_t-unsafe-at-any-size/#comment-28 No, damn :( But thanks for that hint. Damn trap. I tried to omit using UTF-8 (because it makes only sense as an input/output format when writing to files, internally UCS-16 is totally ok). Damn, damn damn damn. BTW: I currently try to port some thousands lines of win32 code to mac os x. No, damn :(

But thanks for that hint.

Damn trap. I tried to omit using UTF-8 (because it makes only sense as an input/output format when writing to files, internally UCS-16 is totally ok). Damn, damn damn damn.

BTW: I currently try to port some thousands lines of win32 code to mac os x.

]]> By: spitgirl http://losingfight.com/blog/2006/07/28/wchar_t-unsafe-at-any-size/comment-page-1/#comment-27 spitgirl Mon, 31 Jul 2006 17:31:55 +0000 http://www.losingfight.com/blog/2006/07/28/wchar_t-unsafe-at-any-size/#comment-27 Nice ending comment, for a guy who's dating a former internationalization engineer. ;) Nice ending comment, for a guy who’s dating a former internationalization engineer. ;)

]]>