|
From: | Cyril ADRIAN |
Subject: | Re: [Liberty-eiffel] Happy new year |
Date: | Wed, 21 Jan 2015 16:17:09 +0100 |
- BDW_GC_DEFINE2.mark_native_arrays checks, whether the current live_type has a feature "generation", I guess to optimize the case, that native arrays are only marked once during a mark phase? But isn't "generation" too generic here?
What if such a featurename exists, but it doesn't have the meaning as in the ITERATORs?
And even worse, what if the feature is not in the set of live_features? -> see test/language/test_agent1.e. I think we need to check not only the availability of a feature named "generation", but additionally test whether it is not optimized away. And what, if the generation feature is renamed?
At the end, I think we should check more of the feature, maybe we should even introduce a general concept to call a feature on object modification (to somehow automate the "next_generation" calls in the COLLECTIONS for the iterators)
mhhhhh. I messed up my ABSTRACT_HASHED_DICTIONARY before finding this non-issue... But maybe you can anyhow comment on my questions/ideas.
- I'd like to add the check whether the generation feature is live. Can you tell me how I can a LIVE_TYPE for liveness of a specific feature?
- BDW_GC_DEFINE2.mark_native_arrays doesn't use its parameter. Is this intended and good?
- Is it true, that any class can contain at most one native array?
[Prev in Thread] | Current Thread | [Next in Thread] |