[M3devel] Simple change to WIDECHAR type

[Rodney M. Bates]

On 07/06/2012 01:51 PM, Dragiša Durić wrote:
> And then, turn parsed string literals into broken WIDECHAR TEXTs?
>

Well, yes, that requires fixing WIDECHAR too.  But at least it would
work if you can live within the BMP.

> On Jul 6, 2012, at 6:28 PM, Rodney M. Bates wrote:
>
>> This is the result of the fact that your editor is writing UTF-8, while
>> the compiler is reading in ISO-latin-1, as the language specifies.  This
>> was sensible at the time it was defined, but has been overcome by the
>> advent and proliferation of Unicode.
>>
>> The abstract code point values in the range 16_80..16_FF are indeed the same in
>> Unicode and ISO-latin-1, but the bit encoding rules are different.
>>
>> The simple and correct solution is to fix the compiler so that, like many
>> programs today, it can be told to use one of several encodings when interpreting
>> its input.  Then set it the same as you set your editor.
>>
>> On 07/01/2012 03:52 AM, Dragiša Durić wrote:
>>> Text.Length(Dragiša Durić)= 15
>>>
>>> out from:
>>>    WITH me = W"Dragiša Durić" DO
>>>      IO.Put("Text.Length("&   me&   ")="&   Fmt.Int(Text.Length(me))&   "\n");
>>>    END;
>>>
>>> On Jun 30, 2012, at 8:12 PM, Dragiša Durić wrote:
>>>
>>>> Jay, please explain this to me. My editor creates UTF8 files, for example. What cm3 expects after W" ?
>>>
>>>
>
>