[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-smalltalk] [Pharo-project] Fun with Pharo generated source.st
From: |
Paolo Bonzini |
Subject: |
Re: [Help-smalltalk] [Pharo-project] Fun with Pharo generated source.st |
Date: |
Mon, 06 May 2013 15:31:19 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 |
Il 05/05/2013 12:06, Frank Shearar ha scritto:
> On 5 May 2013 09:54, Paolo Bonzini <address@hidden> wrote:
>> Il 04/05/2013 18:51, Holger Hans Peter Freyther ha scritto:
>>> Hi,
>>>
>>> I am trying to convert/import all of Iliad (since the development had
>>> moved to Pharo) and I stumble up-on an issue I already had when I tried
>>> to convert Aida.
>>>
>>> This[1] monticello file in line 6417 starts to use UCS-4 for a string
>>> and then stops at some characters later. Importing the file using
>>> FileStream is failing in Pharo as well.
>>
>> And how does monticello file it in then?!? I'm adding the Pharo list.
>
> Monticello doesn't use the snapshot. The snapshot's stored in addition
> to the "real" MC stuff, containing the changes that the mcz defines.
>
> It's sorta-kinda like the difference between your working copy and git
> diff HEAD HEAD^. MC uses the latter, the snapshot is the former.
But it's still a Pharo bug that the snapshot makes no sense, right?
For GNU Smalltalk we can simply interpret a NUL as the first byte of an
UTF-32BE character, and convert it to UTF-8. It's really ugly, but with
a suitable comment it can work.
Paolo