-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Super calls not resolved #99
Comments
I remember that there was an issue that I discovered in the Java Parser related to super-Calls not properly resolved. Apparently I did not open an issue on this, just discussed it on gitter. Might be worth finding out if this relates to that or if it is an issue specific to the CPG. |
I figured that this might be somehow JavaParser related, as it is created as a static call, which makes little sense. But I will have to check the root cause in more detail. I would probably just fix it on our side for now, but we can surely pass this on to the JavaParser guys if it really is a problem coming from upstream 👍 |
Can you make a quick check whether this may be resolved in the latest JP version? There are some fixes related to super functions in 3.15.18+, we are at 3.15.10 |
|
I was looking at javaparser/javaparser@5d63f63 which sounded like in general super calls are resolved but not for specific cases |
Ah I just double checked, the method itself is correctly resolved as |
- add inheritance information also for CXX files - split supertypes into superclasses and implemented interfaces -> needed for correct Java super call resolving - automatically add "this" field to dummy records as well - correctly resolve super.call() and BaseName.super.call() according to JLS 13 - unify handling of the dedicated "unknown declarations" translation unit - remove transitive closure for inheritance
Example:
The text was updated successfully, but these errors were encountered: