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

More MapHandler merging tests #27

Closed
GoogleCodeExporter opened this issue Mar 16, 2015 · 1 comment
Closed

More MapHandler merging tests #27

GoogleCodeExporter opened this issue Mar 16, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Verify that r164 solves all merging problems.

The problem: The MapHandler keeps a stack of instances of _Construct.

A problem will occur if a _Construct keeps a reference to a topic which has
been merged. The reference could be used in the type, player, or scope
property. If topics are merged, the MapHandler should replace these
references with the topic which stays in the topic map.

Walking through the stack of constructs and checking if a topic is part of
the stack is not enough, each _Construct has to be checked.

Original issue reported on code.google.com by lars.he...@gmail.com on 26 Jun 2009 at 12:09

@GoogleCodeExporter
Copy link
Author

Seems to be fixed since it causes no problems

Original comment by lars.he...@gmail.com on 5 Apr 2011 at 10:45

  • Changed state: Fixed

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