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

Other language support #195

Open
bobmattax-ontario opened this issue Jul 17, 2017 · 4 comments
Open

Other language support #195

bobmattax-ontario opened this issue Jul 17, 2017 · 4 comments

Comments

@bobmattax-ontario
Copy link

I'm interested in helping build support for other languages.

Is there a basic path that can be taken to get to this point?

I think the basic requirements are some parser that can take a code block and turn it into an AST, right?
Is there a way to plug that into this library?

Any help/guidance is appreciated.

@ABaldwinHunter
Copy link
Contributor

@bobmattax-ontario Thank you for your zeal! What languages did you want to see supported?

@bobmattax-ontario
Copy link
Author

I'm interested in making contributions related to Intersystems Cache

@ABaldwinHunter
Copy link
Contributor

For context: we actually have been working on some changes to the codeclimate-duplication engine that should make adding additional languages much less work in the future:
https://github.com/codeclimate/codeclimate-duplication/tree/channel/quality-model-beta

We're now using a parser that's in a separate base image. ATM that project is not open source.

The new mechanism is currently being developed. Once it's set, we may go ahead and document an approach to adding language support in the future.

@ABaldwinHunter
Copy link
Contributor

ABaldwinHunter commented Jul 24, 2017

I'm interested in making contributions related to Intersystems Cache

Nice, thanks for the feedback.

To your point, indeed basic requirements for a new language are:

  1. a parser
  2. update that adds this language strategy to the engine, e.g. ruby

If AST is parser output, something is needed to translate the AST into s-expressions (which the wrapped flay tool expects).

edit: stay tuned for more information about the new approach described in my earlier comment 😊

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

2 participants