Sophisticated meta programming in JavaScript, e.g. to build different versions of a library from a single source tree.
JavaScript
Latest commit dc7caf5 Nov 13, 2015 @dcodeIO Merge pull request #6 from oNaiPs/master
Added gulp task project
Permalink
Failed to load latest commit information.
bin 1.0.0 Aug 22, 2014
docs 1.0.0 Aug 22, 2014
tests Added snipping through snip(); snap(); Jan 20, 2014
.gitignore metac standalone compiler Jan 14, 2014
LICENSE Initial Jan 13, 2014
MetaScript.js 1.0.0 Aug 22, 2014
MetaScript.png README Jan 13, 2014
README.md Added gulp task project Nov 12, 2015
donate.png 1.0.0 Aug 22, 2014
example.jpg README Jan 18, 2014
flowchart.jpg Docs Jan 20, 2014
index.js 1.0.0 Aug 22, 2014
jsdoc.json 1.0.0 Aug 22, 2014
package.json 1.0.0 Aug 22, 2014

README.md

MetaScript

Metaprogramming is the writing of computer programs that write or manipulate other programs (or themselves) as their data, or that do part of the work at compile time that would otherwise be done at runtime.

MetaScript is a tool for build time meta programming using JavaScript as the meta language. Written between the lines it enables developers to transform sources in pretty much every way possible.

Donate

How does it work?

If you already know JavaScript, adding some meta is as simple as remembering that:

  • //? begins a line of meta.
  • /*? begins a block of meta and */ ends it.
  • //?... begins a snippet of meta and //?. ends it.
  • ?= writes the expression's raw result to the document.
  • ?== writes the expression's typed result to the document (runs it through JSON.stringify).

MetaScript then turns the meta inside out, making it the actual program, that outputs the contents in between.

A simple example

Let's assume that you have a library and that you want its version number to be included as the constant MyLibrary.VERSION. With meta, this is as simple as:

MyLibrary.VERSION = /*?== VERSION */;
// or, alternatively, if VERSION is always string-safe:
MyLibrary.VERSION = "/*?= VERSION */";

This is what the meta program, when compiled, will look like:

  write('MyLibrary.VERSION = ');
write(JSON.stringify(VERSION));
  write(';\n');

Accordingly, a transformation of the source done by running that exact meta program with a scope of { VERSION: "1.0" } will result in:

MyLibrary.VERSION = "1.0";

It's just that simple and everything else is, of course, up to your imagination.

Advanced examples

Of course it's possible to do much more with it, like declaring macros and defining an entire set of useful utility functions, just like with any sort of preprocessor:

That's a globally available utility function as a snippet:

//?...
simpleIncludeExample = function(file) {
    write(indent(require("fs").readFileSync(file).toString("utf8")), __);
}
//?.

or, as a block:

/*? simpleIncludeExample = function(file) {
    write(indent(require("fs").readFileSync(file).toString("utf8")), __);
} */

Using it:

//? simpleIncludeExample("some/other/file.js")

This is, of course, just an example. See built-in utility for what's actually available out of the box.

That's a globally available macro using inline blocks:

//? ASSERT_OFFSET = function(varname) {
    if (/*?= varname */ < 0 || /*?= varname */ > this.capacity()) {
        throw RangeError("Illegal /*?= varname */");
    }
//? }

Using it:

function writeInt8(value, offset) {
    //? ASSERT_OFFSET('offset');
    ...
}

Results in:

function writeInt8(value, offset) {
    if (offset < 0 || offset > this.capacity()) {
        throw RangeError("Illegal offset");
    }
    ...
}

Some examples are available in the tests folder. While these are JavaScript examples, MetaScript should fit nicely with any other programming language that uses // ... and /* ... */ style comments.

API

The API is pretty much straight forward:

  • new MetaScript(source:string, filename:string)
    Creates a new instance with source, located at filename, compiled to a meta program.
  • MetaScript#program
    Contains the meta program's source.
  • MetaScript#transform(scope:Object):string
    Runs the meta program in the current context, transforming the source depending on what's defined in scope and returns the final source.

One step compilation / transformation:

  • MetaScript.compile(source:string):string
    Compiles the specified source to a meta program and returns its source.
  • MetaScript.transform(source:string, filename:string, scope:Object):string
    Compiles source, located at filename, to a meta program and transforms it using the specified scope in a new VM context.

Command line

Transforming sources on the fly is simple with node:

npm install -g metascript

 Usage: metascript sourcefile -SOMEDEFINE="some" -OTHERDEFINE="thing" [> outfile]

And in the case that you have to craft your own runtime, the raw compiler is also available as metac:

 Usage: metac sourcefile [> outfile]

Built-in utility

There are a few quite useful utility functions available to every meta program:

  • write(contents:string)
    Writes some raw data to the resulting document, which is equal to using /*?= contents */.

  • writeln(contents:string)
    Writes some raw data, followed by a line break, to the resulting document, which is equal to using //?= __+contents.

  • dirname(filename:string)
    Gets the directory name from a file name.

  • include(filename:string, absolute:boolean=)
    Includes another source file or multiple ones when using a glob expression. absolute defaults to false (relative)

  • indent(str:string, indent:string|number):string indents a block of text using the specified indentation given either as a whitespace string or number of whitespaces to use.

  • escapestr(str:string):string
    Escapes a string to be used inside of a single or double quote enclosed JavaScript string.

  • snip()
    Begins a snipping operation at the current offset of the output.

  • snap():string
    Ends a snipping operation, returning the (suppressed) output between the two calls to snip() and snap().

Additionally, there are a few internal variables. Most notably there is the variable __ (2x underscore) that remembers the current indentation level. This is used for example to indent included sources exactly like the meta block that contains the include call.

Using utility dependencies

In case this isn't obvious: Add the dependency to your package.json and, in MetaScript, use:

//? myutility = require('metascript-myutility')

Usage as a task

Documentation

License: Apache License, Version 2.0 - http://www.apache.org/licenses/LICENSE-2.0.html