Why UTF-8/16 character encodings?

H. S. Teoh hsteoh at quickfur.ath.cx
Mon Jun 17 11:47:56 PDT 2013


On Mon, Jun 17, 2013 at 11:37:18AM -0700, Sean Kelly wrote:
> On Jun 5, 2013, at 6:21 PM, Brad Roberts <braddr at puremagic.com> wrote:
> 
> > On 6/5/13 6:11 PM, Timothee Cour wrote:
> >> currently std.demangle.demangle doesn't work with unicode (see example below)
> >> 
> >> If we decide to keep allowing unicode symbols (as opposed to just unicode strings/comments), we must
> >> address this issue. Will supporting this negatively impact performance (of both compile time and
> >> runtime) ?
> >> 
> >> Likewise, will linkers + other tools (gdb etc) be happy with unicode in mangled names?
> >> 
> >> ----
> >> structA{
> >> intz;
> >> voidfoo(intx){}
> >> voidさいごの果実(intx){}
> >> voidªå(intx){}
> >> }
> >> mangledName!(A.さいごの果実).demangle.writeln;=>_D4util13demangle_funs1A18さいごの果実MFiZv
> >> ----
> > 
> > Filed in bugzilla?
> 
> http://d.puremagic.com/issues/show_bug.cgi?id=10393
> https://github.com/D-Programming-Language/druntime/pull/524

Do linkers actually support 8-bit symbol names? Or do these have to be
translated into ASCII somehow?


T

-- 
We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare.  Now, thanks to the Internet, we know this is not true. -- Robert Wilensk


More information about the Digitalmars-d mailing list