How to Add a New Parser to Exuberant Ctags

Exuberant Ctags has been designed to make it very easy to add your own custom language parser.

Operational background

As ctags considers each file name, it tries to determine the language of the file by applying the following three tests in order: if the file extension has been mapped to a language, if the file name matches a shell pattern mapped to a language, and finally if the file is executable and its first line specifies an interpreter using the Unix-style "#!" specification (if supported on the platform). If a language was identified, the file is opened and then the appropriate language parser is called to operate on the currently open file. The parser parses through the file and whenever it finds some interesting token, calls a function to define a tag entry.

Integrating a new parser

Let's assume that I want to add support for my new language, Swine, the successor to Perl (i.e. Perl before Swine <wince>).

First, I create a new module, swine.c, and add one externally visible function to it, extern parserDefinition *SwineParser(void), and add its name to the table in parsers.h. The job of this parser definition function is to create an instance of the parserDefinition structure (using parserNew()) and populate it with information defining how files of this language are recognized, what kinds of tags it can locate, and the function used to invoke the parser on the currently open file.

The structure parserDefinition allows assignment of the following fields:

  const char *name;               /* name of language */
  kindOption *kinds;              /* tag kinds handled by parser */
  unsigned int kindCount;         /* size of `kinds' list */
  const char *const *extensions;  /* list of default extensions */
  const char *const *patterns;    /* list of default file name patterns */
  parserInitialize initialize;    /* initialization routine, if needed */
  simpleParser parser;            /* simple parser (common case) */
  rescanParser parser2;           /* rescanning parser (unusual case) */
  boolean regex;                  /* is this a regex parser? */

The name field must be set to a non-empty string. Also, unless regex is set true (see below), either parser or parser2 must set to point to a parsing routine which will generate the tag entries. All other fields are optional.

Now all that is left is to implement the parser. In order to do its job, the parser should read the file stream using using one of the two I/O interfaces: either the character-oriented fileGetc(), or the line-oriented fileReadLine(). When using fileGetc(), the parser can put back a character using fileUngetc(). How our Swine parser actually parses the contents of the file is entirely up to the writer of the parser--it can be as crude or elegant as desired. You will note a variety of examples from the most complex (c.c) to the simplest (make.c).

When the Swine parser identifies an interesting token for which it wants to add a tag to the tag file, it should create a tagEntryInfo structure and initialize it by calling initTagEntry(), which initializes defaults and fills information about the current line number and the file position of the beginning of the line. After filling in information defining the current entry (and possibly overriding the file position or other defaults), the parser passes this structure to makeTagEntry().

Instead of writing a parser, it may be possible to specify regular expressions which define the tags. In this case, instead of defining a parsing function, SwineParser(), sets regex to true, and points initialize to a function which calls addLanguageRegex() to install the regular expressions which define its tags.

This is all there is to it. All other details are specific to the parser and how it wants to do its job. There are some support functions which can take care of some commonly needed parsing tasks, such as keyword table lookups (see keyword.c), which you can make use of if desired (examples of its use can be found in c.c, eiffel.c, and fortran.c). Almost everyting is already taken care of automatically for you by the infrastructure. Writing the actual parsing algorithm is the hardest part, but is not constrained by any need to conform to anything in ctags other than that mentioned above.

There are several different approaches used in the parsers inside Exuberant Ctags and you can browse through these as examples of how to go about it.

Examples

Below you will find two example parsers. The first is for our mythical Swine parser, which provides tags for lines beginning with "def" followed by some name. The second is a simple regex parser for makefile macros.

/***************************************************************************
 * swine.c
 * Parser for Swine definitions
 **************************************************************************/
/* INCLUDE FILES */
#include "general.h"    /* always include first */

#include <string.h>     /* to declare strxxx() functions */
#include <string.h>     /* to define isxxx() macros */

#include "parse.h"      /* always include */
#include "read.h"       /* to define file fileReadLine() */

/* DATA DEFINITIONS */
typedef enum eSwineKinds {
    K_DEFINE
} swineKind;

static kindOption SwineKinds [] = {
    { TRUE, 'd', "definition", "pig definition" }
};

/* FUNCTION DEFINITIONS */

static void findSwineTags (void)
{
    vString *name = vStringNew ();
    const unsigned char *line;

    while ((line = fileReadLine ()) != NULL)
    {
        /* Look for a line beginning with "def" followed by name */
        if (strncmp ((const char*) line, "def", (size_t) 3) == 0  &&
            isspace ((int) line [3]))
        {
            const unsigned char *cp = line + 4;
            while (isspace ((int) *cp))
                ++cp;
            while (isalnum ((int) *cp)  ||  *cp == '_')
            {
                vStringPut (name, (int) *cp);
                ++cp;
            }
            vStringTerminate (name);
            makeSimpleTag (name, SwineKinds, K_DEFINE);
            vStringClear (name);
        }
    }
    vStringDelete (name);
}

/* Create parser definition stucture */
extern parserDefinition* SwineParser (void)
{
    static const char *const extensions [] = { "swn", NULL };
    parserDefinition* def = parserNew ("Swine");
    def->kinds      = SwineKinds;
    def->kindCount  = KIND_COUNT (SwineKinds);
    def->extensions = extensions;
    def->parser     = findSwineTags;
    return def;
}

/***************************************************************************
 * make.c
 * Regex-based parser for makefile macros
 **************************************************************************/
/* INCLUDE FILES */
#include "general.h"    /* always include first */
#include "parse.h"      /* always include */

/* FUNCTION DEFINITIONS */

static void installMakefileRegex (const langType language)
{
    addLanguageRegex (language, "/(^|[ \t])([A-Z0-9_]+)[ \t]*:?=/\\2/m,macro/i");
}

/* Create parser definition stucture */
extern parserDefinition* MakefileParser (void)
{
    static const char *const patterns [] = { "[Mm]akefile", NULL };
    static const char *const extensions [] = { "mak", NULL };
    parserDefinition* const def = parserNew ("Makefile");
    def->patterns   = patterns;
    def->extensions = extensions;
    def->initialize = installMakefileRegex;
    def->regex      = TRUE;
    return def;
}

Back to Exuberant Ctags