- 
                Notifications
    
You must be signed in to change notification settings  - Fork 11
 
Contributing
        Chase Willden edited this page Nov 17, 2016 
        ·
        5 revisions
      
    There are a few ways to contributing:
- Generating pull requests for the CondorLang c++ code
 - Creating documentation and updating the wiki
 - Creating libraries. People like interfacing with libraries instead of creating them from scratch
 - Submit an Issue for a feature request or an issue
 - Adding comments in the code
 
When pushing code, use the version utility found in utils/version.py. Running the file will increment the BUG version. Argument -a increments MAJOR version. -i MINOR version.
If you would like to contribute to the CondorLang project, pull requests are always welcome. The folder structure goes as follows:
- src (source code)
 - ast (abstract syntax tree related files)
 - error (error files)
 - mem (memory related files)
 - parser (the basic parser from code -> ast -> syntax analysis)
 - scanner (the lexical analysis)
 - semantics (the semantics analysis)
 - token (the token related files, see scanner)
 - 
types (intended for all internal .cb files and the interface with c++)
- array (internal array files)
 - console (internal console files)
 - script (internal scripting, this is the backend how the string is compiled into the code)
 - string (internal string files)
 - try_catch (internal try_catch files)
 - vector (internal vector files)