Skip to content
This repository has been archived by the owner on Mar 10, 2024. It is now read-only.

Resolution of anonymous classes is inaccurate #54

Open
lmove opened this issue Oct 16, 2019 · 1 comment
Open

Resolution of anonymous classes is inaccurate #54

lmove opened this issue Oct 16, 2019 · 1 comment
Labels
question Further information is requested

Comments

@lmove
Copy link
Contributor

lmove commented Oct 16, 2019

In the bytecode M3 model we have:

|java+class:///pkg/A$1|
|java+class:///pkg/A$2|

In the src M3 model we have:

|java+anonymousClass:///pkg/A/m1()/$anonymous1|
|java+anonymousClass:///pkg/A/m2()/$anonymous1|

Given that in the M3 model we manage sets the order is lost, so we cannot pinpoint which is the real method owning the anonymous class anymore.

@lmove lmove added the question Further information is requested label Oct 16, 2019
@lmove
Copy link
Contributor Author

lmove commented Oct 17, 2019

Should we point to the parent class every time we have a location pointing to an anonymous class or an entity contained by it?

@lmove lmove changed the title Resolving physical location of anonymous classes is inaccurate Resolution of anonymous classes is inaccurate Oct 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant