[M3devel] This disgusting TEXT business
Mika Nystrom
mika at async.caltech.edu
Wed Dec 24 01:41:20 CET 2008
Sorry, I think I misinterpreted what you meant by "built-in type".
Darko writes:
>Those don't involve data stored in files, can be fixed with a
>recompile and are only an issue if you reveal the object
>implementation of TEXT.
>
>On 24/12/2008, at 9:29 AM, Mika Nystrom wrote:
>
>> Darko writes:
>>> Besides breaking pickles (which isn't minor to those it affects) it
>>> also has the effect of doubling the size of String16 arrays and any
>>> wide strings or arrays. Why change the meaning of an existing type,
>>> possibly breaking unknown software when we can just define another
>>> type? It's not like another built-in type will cause anyone problems.
>>
>> stubgen, stablegen, ... :-) no free lunch here, I'm afraid.
>>
>>>
>>> On 24/12/2008, at 6:15 AM, Mika Nystrom wrote:
>>>
>>>> "Rodney M. Bates" writes:
>>>> ...
>>>>> It ought to cause minimal grief to just change WIDECHAR so it has a
>>>>> big enough value range for all the Unicode values, probably 32 bits
>>>>> in today's world. Surely nobody has written any code that assumes
>>>>> BITSIZE(WIDECHAR)=16. ;-) Even if so, this shouldn't be a terribly
>>>> ...
>>>>
>>>> Minor issue, I know, but... Pickles?
>>>>
>>>> Mika
More information about the M3devel
mailing list