Hi all,
The method that generated the error in issue 3090 is below:


MethodContext(ContextPart)>>storeDataOn: aDataStream

    "Contexts are not allowed go to out in DataStreams.  They must be included inside an ImageSegment."

    aDataStream insideASegment ifTrue: [^ super storeDataOn: aDataStream].

    self error: 'This Context was not included in the ImageSegment'.
        "or perhaps ImageSegments were not used at all"
    ^ nil


I've been trying to make sense of the stack, and it appears that writing a morph
to a file is hooking at least one extra object, which cannot be written to a DataStream.

Does anyone know whether the proper behavior is to:
- have the context go out without being inside an ImageSegment, or
- fix the morph-writing so that it uses ImageSegments???

Or perhaps there's a better way to understand the stack.

Many thanks,
and Cheers,

Sheri/dan


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to