Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AST or bytecode #1

Closed
yegor256 opened this issue Oct 16, 2017 · 4 comments
Closed

AST or bytecode #1

yegor256 opened this issue Oct 16, 2017 · 4 comments

Comments

@yegor256
Copy link
Member

To calculate class cohesion metrics we need information about methods, attributes, and connections between them. We can get that from the bytecode directly, or from AST, which we should get through some parser. Which option is better? The decision is important, since it will affect the entire design of this tool.

@witek1902
Copy link

PoC for both options? ;)

@yegor256
Copy link
Member Author

@witek1902 that will be too expensive) We may also not be able to realize in the beginning what potential issues each approach will have later. So, it's better to make one mistake and stick to it)

@yegor256
Copy link
Member Author

javassist seems to be working just fine.

@0crat
Copy link
Collaborator

0crat commented Oct 17, 2017

I'm not managing yegor256/jpeek GitHub repository. You have to contact me in Slack first. Our policy explains how.

rultor pushed a commit that referenced this issue Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants