Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dictionary backtracking compatibility with Squeak (trunk) #548

Closed
GoogleCodeExporter opened this issue Mar 25, 2015 · 4 comments
Closed

Comments

@GoogleCodeExporter
Copy link

In recent Squeak versions, Dictionary is no longer a subclass of Set, 
therefore it's necessary to copy the methods #snapshotCopy and 
#restoreFromSnapshot: from Set to Dictionary, otherwise backtracking breaks 

Original issue reported on code.google.com by radoslav...@gmail.com on 22 Feb 2010 at 8:53

@GoogleCodeExporter
Copy link
Author

I assume WABacktrackingTest is failing?

Is it time for someone to create Seaside-Squeak-Core? Or should we put these 
methods
on both classes in Seaside-Pharo-Core?

Original comment by jfitz...@gmail.com on 22 Feb 2010 at 9:13

  • Changed state: Accepted
  • Added labels: Platform-Squeak, Portability, Priority-Critical
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author

Yes WABacktrackingTest is failing. As for Seaside-Squeak-Core, I would be 
willing to 
help maintaining it, but won't it complicate the web packager/builder?

Original comment by radoslav...@gmail.com on 22 Feb 2010 at 9:21

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Squeak will have to provide and maintain their own packager/builder/loader ...

Original comment by renggli on 27 Feb 2010 at 10:17

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Looks like this is resolved now: 
<http://lists.squeakfoundation.org/pipermail/seaside-dev/2010-
March/004034.html>

Original comment by renggli on 5 Apr 2010 at 11:06

  • Changed state: Fixed
  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant