Difference between revisions of "Talk:Void-safe migration guide"
(New page: --~~~~: The problem about not having `default_create' as creation procedure in CELL anymore, even when the actual generic parameter is detachable, is not just an expandedness issue. What d...) |
|||
| Line 1: | Line 1: | ||
| − | --[[User:Ericb|Ericb]] 14:34, 2 August 2009 (UTC): The problem about not having `default_create' as creation procedure in CELL anymore, even when the actual generic parameter is detachable, is not just an expandedness issue. What do we do with code like that: | + | ''--[[User:Ericb|Ericb]] 14:34, 2 August 2009 (UTC)''': The problem about not having `default_create' as creation procedure in CELL anymore, even when the actual generic parameter is detachable, is not just an expandedness issue. What do we do with code like that: |
<eiffel> | <eiffel> | ||
class A [G -> ANY create default_create end] | class A [G -> ANY create default_create end] | ||
| Line 7: | Line 7: | ||
a: A [CELL [detachable FOO]] | a: A [CELL [detachable FOO]] | ||
</eiffel> | </eiffel> | ||
| + | |||
| + | :'''--[[User:Manus|manus]] 18:27, 3 August 2009 (UTC)''': Of course here you have not much choice and you either have to rewrite `A' and/or define a new CELL class that has ''default_create'' as a creation procedure. The real question is how much of this code actually exists and the impact of rewriting the code that depended on that. Another solution is to modify `default_create' in ANY to have a precondition re-definable by descendants so to leave your code unchanged, in this case `CELL' would say it is ok to use ''default_create'' but only when the actual generic parameter is detachable. | ||
Revision as of 09:27, 3 August 2009
--Ericb 14:34, 2 August 2009 (UTC)': The problem about not having `default_create' as creation procedure in CELL anymore, even when the actual generic parameter is detachable, is not just an expandedness issue. What do we do with code like that:
class A [G -> ANY create default_create end] ... end a: A [CELL [detachable FOO]]
- --manus 18:27, 3 August 2009 (UTC): Of course here you have not much choice and you either have to rewrite `A' and/or define a new CELL class that has default_create as a creation procedure. The real question is how much of this code actually exists and the impact of rewriting the code that depended on that. Another solution is to modify `default_create' in ANY to have a precondition re-definable by descendants so to leave your code unchanged, in this case `CELL' would say it is ok to use default_create but only when the actual generic parameter is detachable.
