On 05/14/2012 04:17 PM, Eric Botcazou wrote:
Our normal procedure is to generate a declaration when we see a function
in its enclosing context, and then fix it up later when we see the
definition. Why not handle this similarly?
Because we want to generate an abstract instance of the nested function within
the abstract instance of the parent function. If we wait for the definition of
the nested function, and it's out-of-line, we attach the out-of-line instance
to the abstract parent, which is the source of the problem.
Right, and that's why we want your change to split the nested function
into abstract and concrete instances. But then it should be fine to
attach the abstract instance to the abstract parent normally, I would think.
Jason
