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.

Sign up for GitHub

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

Jump to bottom

Configurations should not hold on to classes #820

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

Configurations should not hold on to classes #820

GoogleCodeExporter opened this issue Mar 25, 2015 · 1 comment
Assignees
@marschall
Labels
auto-migrated Platform-GemStone Priority-Low Type-Portability
Milestone
3.2

Comments

@GoogleCodeExporter
Copy link 

Configurations should directly not hold on to classes because these will be old 
class versions in GemStone/S.

Options include
- holding on to a Symbol and doing a lookup (may have impact for dialects with 
namespaces)
- holding on to the association/binding from Smalltalk

Original issue reported on code.google.com by philippe...@gmail.com on 22 Aug 2014 at 6:38
@GoogleCodeExporter
Copy link
Author 

I encourage this change. Holding onto actual classes makes unloading code more 
difficult in VA Smalltalk.

Original comment by wemb...@instantiations.com on 19 Jan 2015 at 7:21

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

@marschall marschall added this to the 3.2 milestone Jul 12, 2015
@marschall marschall self-assigned this Jul 12, 2015
@dalehenrich dalehenrich mentioned this issue Jul 20, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marschall marschall

Labels
auto-migrated Platform-GemStone Priority-Low Type-Portability
Projects
None yet
Milestone
3.2
Development

No branches or pull requests
2 participants
@marschall @GoogleCodeExporter