AFAIU, Fuel is not capable working across versions, let alone over the
non-spur/spur divide. It's a let down, but it is by design (to optimise for
absolute speed).
> On 15 Oct 2016, at 05:46, Sean P. DeNigris <[email protected]> wrote:
>
> Eliot Miranda-2 wrote
>> Is that character code legal unicode?
>
> No, but that turned out to be a red herring!
>
> This simple experiment seems to show a fundamental problem when serializing
> in 4.0 (non-spur) and materializing in 5.0 (spur):
>
> FileStream forceNewFileNamed: filename do: [:aFile |
> FLSerializer newDefault
> serialize: ($e) on: aFile binary ] .
>
> FLMaterializer materializeFromFileNamed: filename.
>
> Doing the serialization and materialization in the same 4.0 image works, but
> materializing in a 5.0 image throws an error (a different one this time -
> "MessageNotUnderstood: receiver of ""adaptToNumber:andSend:"" is nil")
>
>
>
> -----
> Cheers,
> Sean
> --
> View this message in context:
> http://forum.world.st/Spur-VM-Bug-for-Chinese-Characters-tp4918883p4918909.html
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
>
