Issue with PRSegmentPersistency in Pharo 1.4

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue with PRSegmentPersistency in Pharo 1.4

Reza Razavi
Hi,

When loading "Pier-Pharo-Persistency" in a Pharo 1.4, the following warning is raised:

This package depends on the following classes:
  ImageSegment
You must resolve these dependencies before you will be able to load these definitions:
  writeKernel:on:

Select Proceed to continue, or close this window to cancel the operation.


This is due to a reference to ImageSegment in the following method:

PRSegmentPersistency >> serialize: aString
    | stream pointers |
    stream := self directory forceNewFileNamed: aString.
    pointers := [ [ ImageSegment new writeKernel: self kernel on: stream ]
        ensure: [ stream close ] ] on: Exception do: [ :error | nil ].
    (pointers isNil or: [ pointers anySatisfy: [ :each | (each isLiteral or: [ each isVariableBinding ]) not ] ])
        ifTrue: [ self directory deleteFileNamed: aString ifAbsent: [ ] ]


Would this be worthy to fill a bug report?

Cheers,
Reza


_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Reply | Threaded
Open this post in threaded view
|

Re: Issue with PRSegmentPersistency in Pharo 1.4

Nick
yes or submitted a fix :-)


On 21 September 2012 16:30, Reza Razavi <[hidden email]> wrote:
Hi,

When loading "Pier-Pharo-Persistency" in a Pharo 1.4, the following warning is raised:

This package depends on the following classes:
  ImageSegment
You must resolve these dependencies before you will be able to load these definitions:
  writeKernel:on:

Select Proceed to continue, or close this window to cancel the operation.


This is due to a reference to ImageSegment in the following method:

PRSegmentPersistency >> serialize: aString
    | stream pointers |
    stream := self directory forceNewFileNamed: aString.
    pointers := [ [ ImageSegment new writeKernel: self kernel on: stream ]
        ensure: [ stream close ] ] on: Exception do: [ :error | nil ].
    (pointers isNil or: [ pointers anySatisfy: [ :each | (each isLiteral or: [ each isVariableBinding ]) not ] ])
        ifTrue: [ self directory deleteFileNamed: aString ifAbsent: [ ] ]


Would this be worthy to fill a bug report?

Cheers,
Reza


_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki


_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Reply | Threaded
Open this post in threaded view
|

Re: Issue with PRSegmentPersistency in Pharo 1.4

Mariano Martinez Peck
Just in case someone is interested... Based on Yanni's Fuel Persistency Strategy, I did a VERY simple tool to export/import Pier kernels using Fuel. 

You need to install Fuel first (if you are using Pharo 2.0 it is already there) and then:

Gofer it
squeaksource3: 'pierfuel';
package: 'Pier-FuelPersistence-Core';
package: 'Pier-FuelPersistence-Test';
load.

Then check the methods of  PRFuelExporterImporter.

Cheers,

On Fri, Sep 21, 2012 at 7:21 PM, Nick Ager <[hidden email]> wrote:
yes or submitted a fix :-)


On 21 September 2012 16:30, Reza Razavi <[hidden email]> wrote:
Hi,

When loading "Pier-Pharo-Persistency" in a Pharo 1.4, the following warning is raised:

This package depends on the following classes:
  ImageSegment
You must resolve these dependencies before you will be able to load these definitions:
  writeKernel:on:

Select Proceed to continue, or close this window to cancel the operation.


This is due to a reference to ImageSegment in the following method:

PRSegmentPersistency >> serialize: aString
    | stream pointers |
    stream := self directory forceNewFileNamed: aString.
    pointers := [ [ ImageSegment new writeKernel: self kernel on: stream ]
        ensure: [ stream close ] ] on: Exception do: [ :error | nil ].
    (pointers isNil or: [ pointers anySatisfy: [ :each | (each isLiteral or: [ each isVariableBinding ]) not ] ])
        ifTrue: [ self directory deleteFileNamed: aString ifAbsent: [ ] ]


Would this be worthy to fill a bug report?

Cheers,
Reza


_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki


_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki



--
Mariano
http://marianopeck.wordpress.com


_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki