Re: [PATCH] [Bug c++/49118] fake template nesting for operator-> chain

[Jason Merrill <jason@redhat.com>]

On 06/02/2011 03:25 PM, David Krauss wrote:
> Optimally the re-opened context would be the preceding operator->  function itself, to create the illusion of nested calls. However, the result of build_new_op may be a target_expr or a call_expr. I'm not sure of the best way to recover the function declaration from this ambiguous tree, nor whether it would a performance issue (i.e., too much work for the reward).

For a CALL_EXPR you can use get_callee_fndecl.  I wouldn't object to 
teaching it to handle TARGET_EXPR and AGGR_INIT_EXPR as well.

As for the duplicate error message, that happens because we complain 
when doing push_tinst_level first in instantiate_decl and then again in 
build_x_arrow.  To avoid this we would need to hit each new depth first 
in build_x_arrow, either by pushing and then popping again before the 
call the build_new_op, or adding something like 
suspend/resume_tinst_level to pt.c.

Jason