| Re: [cdt-dev] indexer? hierarchy? querying problem |
That would be cool.
Do you have a pointer to similar code?
update on Nathan track
To get this type of information, you need to get an AST for the file thatI got to the file that contains the code (setup) using the indexer. fighting ITranslationUnit.getAST() right now.
contains the code. You can get one with ITranslationUnit.getAST().
Best regards
Jantje
Op 19/01/2016 om 14:43 schreef Alena Laskavaia:
I think we have some checkers in codan that will look for certain function and validate their arguments, which would be very similar code.
On Tue, Jan 19, 2016 at 6:25 AM, Jan Baeyens <jan@xxxxxxxxxx> wrote:
Nate
Thanks for the answer. From what I understand from your mail it looks perfectly like what I need and I'll try to implement this.
I may have more questions but it'll probably take time as there are plenty of gaps in my understanding I need to fill in.
Best regards
Jantje
Op 19/01/2016 om 8:27 schreef Nathan Ridge:
What I have in its simplest form is this as source code to be parsedGenerally speaking, the index only stores information about declarations.
void setup()
{
Serial.begin(123);
}
What I need to get as result for this case is 123.
I didn't get closer than this code
String variableName = "Serial";
IIndexBinding[] bindings =
index.findBindings(variableName.toCharArray(),
IndexFilter.ALL_DECLARED_OR_IMPLICIT, new NullProgressMonitor());
When variableName is "Serial" or "setup" I get a list of bindings I can
inspect; but how do I get this for "Serial.begin"?
It doesn't store things like information about a function call _expression_
occuring inside a function body.
To get this type of information, you need to get an AST for the file that
contains the code. You can get one with ITranslationUnit.getAST().
Once you have an AST, there are several ways you can get the information
you want. I'll describe one way here:
- Use IASTTranslationUnit.getScope() get the global scope
- Assuming "Serial" is of some type "SerialT" which is defined in the
global scope, use IScope.find(String, IASTTranslationUnit) to find
the binding representing this type. It should implement ICPPClassType.
- Use ICPPClassType.getMethods() to get a list of methods of this type.
Iterate through the list to find the one named "begin".
- Use IASTTranslationUnit.getReferences() on the ICPPMethod representing
the 'begin' method to find all the places where it's called.
- Loop through the references, and examine the surrounding AST to
find the value you need. In your case:
- the reference to 'begin' will be an IASTName
- its parent should be an IASTFieldReference representing 'Serial.begin'
- its parent should be an IASTFunctionCallExpression representing
'Serial.begin(123)'
- the function call _expression_ will have an argument _expression_ of type
IASTLiteralExpression
- IASTLiteralExpression.getValue() will give you the '123'
Hope that helps,
Nate
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev