> On 9 Sep 2017, at 18:00, Sean P. DeNigris wrote:
>
> Sven Van Caekenberghe-2 wrote
>> Implement...
>
> Thanks! I added this to the wiki so we don't lose track of it:
> https://github.com/svenvc/ston/wiki/Cookbook
Cool, thanks.
Sven Van Caekenberghe-2 wrote
> Implement...
Thanks! I added this to the wiki so we don't lose track of it:
https://github.com/svenvc/ston/wiki/Cookbook
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
> On 9 Sep 2017, at 16:11, Sean P. DeNigris wrote:
>
> Sven Van Caekenberghe-2 wrote
>> You would have to change the way the offending object get handled.
>
> Any suggestions on how to do that? Is there a particularly good place to
> hook in?
Implement FileSystem class>>#stonAllInstVarNames to
Sven Van Caekenberghe-2 wrote
> You would have to change the way the offending object get handled.
Any suggestions on how to do that? Is there a particularly good place to
hook in?
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
> On 9 Sep 2017, at 05:44, Sean P. DeNigris wrote:
>
> I was migrating some data from Pharo 4 to Pharo 6.1 and fell over the fact
> that FileSystem has a #workingDirectory instVar in the source, but not in
> the target. I ended up monkey patching STON until the objects were loaded
> and then rev
I was migrating some data from Pharo 4 to Pharo 6.1 and fell over the fact
that FileSystem has a #workingDirectory instVar in the source, but not in
the target. I ended up monkey patching STON until the objects were loaded
and then reverting, but is there a way to skip an inst var via the proper
ST