Why UTF-8/16 character encodings?

[Sean Kelly]

On Jun 17, 2013, at 6:28 PM, Brad Roberts <braddr at puremagic.com> wrote:

> On 6/17/13 11:58 AM, Sean Kelly wrote:
>> On Jun 17, 2013, at 11:47 AM, "H. S. Teoh" <hsteoh at quickfur.ath.cx> wrote:
>>> 
>>> Do linkers actually support 8-bit symbol names? Or do these have to be
>>> translated into ASCII somehow?
>> 
>> Good question.  It looks like the linker on OSX does:
>> 
>> 	public	_D3abc1A18さいごの果実MFiZv
>> 	public	_D3abc1A4ªåMFiZv
>> 
>> The object file linked just fine.  I haven't tried OPTLINK on Win32 though.
>> 
> 
> Don't symbol names from dmd/win32 get compressed if they're too long, resulting in essentially arbitrary random binary data being used as symbol names?  Assuming my memory on that is correct then it's already demonstrated that optlink doesn't care what the data is.

Yes.  So it isn't always possible to fully demangle really long symbol names.  This is not terribly difficult to hit using templates, especially if they take string arguments.