Re: [Pharo-dev] STON: SortedCollection Bug?

2017-09-09 Thread Sven Van Caekenberghe
> On 9 Sep 2017, at 15:45, Sean P. DeNigris wrote: > > Sven Van Caekenberghe-2 wrote >> STON cannot serialise block closures. > > Oops, sorry. I see that now: > https://github.com/svenvc/ston/blob/master/ston-paper.md#limitations > > I wonder, in this case, there are no

Re: [Pharo-dev] STON: SortedCollection Bug?

2017-09-09 Thread Sean P. DeNigris
Sven Van Caekenberghe-2 wrote > STON cannot serialise block closures. Oops, sorry. I see that now: https://github.com/svenvc/ston/blob/master/ston-paper.md#limitations I wonder, in this case, there are no references in the block to any objects except its own arguments. Would it be possible to

Re: [Pharo-dev] STON: SortedCollection Bug?

2017-09-09 Thread Sven Van Caekenberghe
STON cannot serialise block closures. You would have to get creative to make this work. For SortedCollection, it would only work without a sort block. STON fromString: (STON toString: #(1 2 3) asSortedCollection). > On 9 Sep 2017, at 04:58, Sean P. DeNigris wrote: >

[Pharo-dev] STON: SortedCollection Bug?

2017-09-08 Thread Sean P. DeNigris
I serialized aSortedCollection with a sort block comparing via a #startTime message on the domain objects. When I attempted to materialize it, I got an error that my domain objects don't understand #<=. It seems that the elements are being loaded before the sort block. - Cheers, Sean --