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 |
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")
View this message in context:
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.