Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Resolving overloaded 'operator ()' binding

I agree, we should have a public API ICPPASTFunctionCallExpression.getOverload().

Could you file a bug for this?


> Date: Wed, 13 Aug 2014 14:17:29 +0400 
> From: dmitrynpetrov@xxxxxxxxx 
> To: cdt-dev@xxxxxxxxxxx 
> Subject: Re: [cdt-dev] Resolving overloaded 'operator ()' binding 
> ...Ok, CPPASTFunctionCallExpression#getOverload() does it. 
> Looks like it should be a part of ICPPASTFunctionCallExpression. 
> On Wed, Aug 13, 2014 at 12:43 PM, Dmitry Petrov  
> <dmitrynpetrov@xxxxxxxxx<mailto:dmitrynpetrov@xxxxxxxxx>> wrote: 
> Suppose I have an ICPPASTFunctionCallExpression expression representing  
> overloaded 'operator ()' call. 
> Finding proper 'operator()' binding can get quite tough with all  
> overloads, implicit casts, and so on. 
> I suppose CDT does something about it (otherwise it would be unable to  
> perform type check for such expressions, and resolve bindings that  
> depend on the type of this expression). 
> The same question can be applied to other overloaded operator calls  
> that are represented as "regular" expressions in CDT AST. 
> For ICPPASTBinaryExpression (and so on), the answer is  
> ICPPASTBinaryExpression#getOverload(). 
> Unfortunately, there's no similar method in ICPPASTFunctionCallExpression. 
> Is there any code in CDT that could be reused? 
> _______________________________________________ cdt-dev mailing list  
> cdt-dev@xxxxxxxxxxx To change your delivery options, retrieve your  
> password, or unsubscribe from this list, visit  

Back to the top