Language contributor checklist

    The name of the file is used as a short language identifier and should be usable as a class name in HTML and CSS.

    2. Provide meta data

    At the top of the file there is a specially formatted comment with meta data processed by a build system.Meta data format is simply key-value pairs each occupying its own line:

    1. /*
    2. Requires: java.js, sql.js
    3. Author: John Smith <email@domain.com>
    4. Contributors: Mike Johnson <...@...>, Matt Wilson <...@...>
    5. */

    — a list of other language files required for this language to work.This make it possible to describe languages that extend definitions of other ones.Required files aren’t processed in any special way.The build system just makes sure that they will be in the final package in object.

    The meaning of the other headers is pretty obvious.

    Take inspiration from other languages in and read for more details.

    4. Write class reference

    Class reference lives in the ..Describe shortly names of all meaningful modes used in your language definition.

    6. Create a pull request

    Send your contribution as a pull request on GitHub.