Multi interpreter language support

Issue #38 new
Alejandro Claro Mosqueda created an issue

It would be nice if the language interpreter for rules and transform were an extension point.

There is a fork (Vera--) with support for Lua language instead of TCL, but for example, I am working on a project were all scripts are usually written in python.

I could do this change if your are interested in add this feature.

Comments (7)

  1. Gaëtan Lehmann

    Hi alcaro,

    I'm afraid we completely missed your message, and we'd like to apologize for that.

    Of course we are very interested in this contribution, and would be pleased to help you in this task. We don't have yet any process on how to coordinate some external developments — we can begin to communicate by mail if you have some questions and see how it goes :)

    Gaëtan

  2. Alejandro Claro Mosqueda reporter

    Hi Mr Lehmann,

    I am very interested in Vera++. i am using it a lot. At this moment I have 15 additional rules, and about 50 pending.

    I am having some troubles with more elaborated rules. So I am also interested in add some features and utilities to the API in order to simplified some common task in this rules and get more information available through boost wave lexer:

    • Namespace, Class, Struct, Enum, Function, Variable, Constants, Defines, Scope identifiers.
    • Utility functions found in google cppclean.py.

    It is possible to create a branch in your repository for this changes?

    I am starting to evaluate the features to develop and the adjustments required to add the python interpreter option.

    What do you think? It is possible to get a branch to commit changes so you can evaluate the possibility to incorporate this features into your project?

    Thank in advance, Alejandro

  3. Gaëtan Lehmann

    Sure we can give you access to a branch. Could you give us a branch name that you'd like to use, so we can configure the write access?

  4. Alejandro Claro Mosqueda reporter

    Do you have any branching policy? per feature or per developer?

    I think that at this moment the simplest thing is a branch for me as developer. The name could be my user name "aclaro".

    What do you think?

  5. Gaëtan Lehmann

    We don't have such policy yet - we'll be experimenting :-) I'm creating the alcaro branch…

  6. Log in to comment