[ansi-test-devel] read-symbol.13 test?

[Raymond Toy]

On 4/16/10 6:05 PM, Tobias C. Rittweiler wrote:
> Raymond Toy <toy.raymond at gmail.com> writes:
>
>   
>> In read-symbol.13, the test creates a symbol from a single character and
>> expects that the symbol-name of the symbol is exactly the same as
>> specified character.
>>
>> CMUCL fails this test because intern, make-symbol, and friends convert
>> the string to Unicode NFC form first.  This conversion usually produces
>> the same string, but, for example, #\Combining_Grave_Tone_Mark (U+0340)
>> produces the symbol whose name is #\Combining_Grave_Accent.
>>
>> I couldn't find anything that says that the string name of the symbol
>> must be exactly the same as the given string.
>>
>> Ray
>>     
> How do you read the dictionary entry for INTERN differently than saying
> that?
>
>   intern enters a symbol named string into package. If a symbol whose
>   name is the same as string is already accessible in package, it is
>   returned. If no such symbol is accessible in package, a new symbol
>   with the given name is created ...
>   
That seems pretty clear.  CMUCL's rational for doing this is that from
the Unicode view, the order of the combining marks is not important for
the string, so CMUCL converts the string to a NFC form.

Ray