# Parsing Expressions

## Turning text into code

Terms defined: Turing Machine, YAML, finite state machine, literal, parser, precedence, token, well formed

In we created regular expressions by constructing objects. It takes a lot less typing to write them as strings as we did for HTML selectors, but if we're going to do that we need something to convert those strings to the required objects. In other words, we need to write a parser.

Regular expression grammar.
Meaning Character
Any literal character c c
Beginning of input ^
End of input $Zero or more of the previous thing * Either/or | Grouping (…) shows the grammar we will handle. When we are done we should be able to parse /^(a|b|$)*z$/ as "start of text", "any number of 'a', 'b', or '$'", "a single 'z', and "end of text". (We write regular expressions inside slashes to distinguish them from strings.) To keep things simple, we will create a tree of objects () rather than instances of the regular expression classes from ; the exercises will tackle the latter.

### Please don't write parsers

Languages that are comfortable for people to read are usually difficult for computers to understand and vice versa, so we need parsers to translate human-friendly notation into computer-friendly representations. However, the world doesn't need more file formats; if you need a configuration file or lookup table, please use CSV, JSON, YAML, or something else that already has an acronym rather than inventing a format of your own.

## How can we break text into tokens?

A token is an atom of text, such as the digits making up a number or the letters making up a variable name. In our grammar the tokens are the special characters *, |, (, ), ^, and $, plus any sequence of one or more other characters (which count as one multi-letter token). This classification guides the design of our parser: 1. If a character is special, create a token for it. 2. If it is a literal then: 1. combine it with the current literal if there is one, or 2. start a new literal. 3. Since ^ and $ are either special or regular depending on position, we must treat them as separate tokens or as part of a literal based on where they appear.

We can translate these rules almost directly into code to create a list of objects whose keys are kind and loc (short for location), with the extra key value for literal values:

const SIMPLE = {
'*': 'Any',
'|': 'Alt',
'(': 'GroupStart',
')': 'GroupEnd'
}

const tokenize = (text) => {
const result = []
for (let i = 0; i < text.length; i += 1) {
const c = text[i]
if (c in SIMPLE) {
result.push({ kind: SIMPLE[c], loc: i })
} else if (c === '^') {
if (i === 0) {
result.push({ kind: 'Start', loc: i })
} else {
combineOrPush(result, c, i)
}
} else if (c === '$') { if (i === (text.length - 1)) { result.push({ kind: 'End', loc: i }) } else { combineOrPush(result, c, i) } } else { combineOrPush(result, c, i) } } return result } export default tokenizetokenizer-collapse.js The helper function combineOrPush does exactly what its name says. If the thing most recently added to the list of tokens isn't a literal, the new character becomes a new token; otherwise, we append the new character to the literal we're building:  const combineOrPush = (soFar, character, location) => { const topIndex = soFar.length - 1 if ((soFar.length === 0) || (soFar[topIndex].token !== 'Lit')) { soFar.push({ kind: 'Lit', value: character, loc: location }) } else { soFar[topIndex].value += character } }tokenizer-collapse.js We can try this out with a three-line test program: import tokenize from './tokenizer-collapse.js' const test = '^a^b*' const result = tokenize(test) console.log(JSON.stringify(result, null, 2)) tokenizer-collapse-example.js [ { "kind": "Start", "loc": 0 }, { "kind": "Lit", "value": "a", "loc": 1 }, { "kind": "Lit", "value": "^", "loc": 2 }, { "kind": "Lit", "value": "b", "loc": 3 }, { "kind": "Any", "loc": 4 } ] tokenizer-collapse-example.out This simple tokenizer is readable, efficient, and wrong. The problem is that the expression /ab*/ means "a single a followed by zero or more b". If we combine the a and b as we read them, though, we wind up with "zero or more repetitions of ab". (Don't feel bad if you didn't spot this: we didn't notice the problem until we were implementing the next step.) The solution is to treat each regular character as its own literal in this stage and then combine things later. Doing this lets us get rid of the nested if for handling ^ and $ as well:

const SIMPLE = {
'*': 'Any',
'|': 'Alt',
'(': 'GroupStart',
')': 'GroupEnd'
}

const tokenize = (text) => {
const result = []
for (let i = 0; i < text.length; i += 1) {
const c = text[i]
if (c in SIMPLE) {
result.push({ kind: SIMPLE[c], loc: i })
} else if ((c === '^') && (i === 0)) {
result.push({ kind: 'Start', loc: i })
} else if ((c === '$') && (i === (text.length - 1))) { result.push({ kind: 'End', loc: i }) } else { result.push({ kind: 'Lit', loc: i, value: c }) } } return result } export default tokenize tokenizer.js Software isn't done until it's tested, so let's build some Mocha tests for our tokenizer. The listing below shows a few of these along with the output for the full set: import assert from 'assert' import tokenize from '../tokenizer.js' describe('tokenizes correctly', async () => { it('tokenizes a single character', () => { assert.deepStrictEqual(tokenize('a'), [ { kind: 'Lit', value: 'a', loc: 0 } ]) }) it('tokenizes a sequence of characters', () => { assert.deepStrictEqual(tokenize('ab'), [ { kind: 'Lit', value: 'a', loc: 0 }, { kind: 'Lit', value: 'b', loc: 1 } ]) }) it('tokenizes start anchor alone', () => { assert.deepStrictEqual(tokenize('^'), [ { kind: 'Start', loc: 0 } ]) }) it('tokenizes start anchor followed by characters', () => { assert.deepStrictEqual(tokenize('^a'), [ { kind: 'Start', loc: 0 }, { kind: 'Lit', value: 'a', loc: 1 } ]) }) it('tokenizes a complex expression', () => { assert.deepStrictEqual(tokenize('^a*(bcd|e^)*f$gh$'), [ { kind: 'Start', loc: 0 }, { kind: 'Lit', loc: 1, value: 'a' }, { kind: 'Any', loc: 2 }, { kind: 'GroupStart', loc: 3 }, { kind: 'Lit', loc: 4, value: 'b' }, { kind: 'Lit', loc: 5, value: 'c' }, { kind: 'Lit', loc: 6, value: 'd' }, { kind: 'Alt', loc: 7 }, { kind: 'Lit', loc: 8, value: 'e' }, { kind: 'Lit', loc: 9, value: '^' }, { kind: 'GroupEnd', loc: 10 }, { kind: 'Any', loc: 11 }, { kind: 'Lit', loc: 12, value: 'f' }, { kind: 'Lit', loc: 13, value: '$' },
{ kind: 'Lit', loc: 14, value: 'g' },
{ kind: 'Lit', loc: 15, value: 'h' },
{ kind: 'End', loc: 16 }
])
})
})test/test-tokenizer.js

> stjs@1.0.0 test /u/stjs
> mocha */test/test-*.js "-g" "tokenizes correctly"

tokenizes correctly
✓ tokenizes a single character
✓ tokenizes a sequence of characters
✓ tokenizes start anchor alone
✓ tokenizes start anchor followed by characters
✓ tokenizes circumflex not at start
✓ tokenizes start anchor alone
✓ tokenizes end anchor preceded by characters
✓ tokenizes dollar sign not at end
✓ tokenizes repetition alone
✓ tokenizes repetition in string
✓ tokenizes repetition at end of string
✓ tokenizes alternation alone
✓ tokenizes alternation in string
✓ tokenizes alternation at start of string
✓ tokenizes the start of a group alone
✓ tokenizes the start of a group in a string
✓ tokenizes the end of a group alone
✓ tokenizes the end of a group at the end of a string
✓ tokenizes a complex expression

19 passing (12ms)

tokenizer-test.out

## How can we turn a list of tokens into a tree?

We now have a list of tokens, but we need a tree that captures the nesting introduced by parentheses and the way that * applies to whatever comes before it. Let's trace a few cases in order to see how to build this tree:

1. If the regular expression is /a/, we create a Lit token for the letter a (where "create" means "append to the output list").

2. What if the regular expression is /a*/? We first create a Lit token for the a and append it to the output list. When we see the *, we take that Lit token off the tail of the output list and replace it with an Any token that has the Lit token as its child.

3. Our next thought experiment is /(ab)/. We don't know how long the group is going to be when we see the (, so we put the parenthesis onto the output as a marker. We then add the Lit tokens for the a and b until we see the ), at which point we pull tokens off the end of the output list until we get back to the ( marker. When we find it, we put everything we have temporarily collected into a Group token and append it to the output list. This algorithm automatically handles /(a*)/ and /(a(b*)c)/.

4. What about /a|b/? We append a Lit token for a, get the | and—and we're stuck, because we don't yet have the next token we need to finish building the Alt.

One way to solve this problem is to check to see if the thing on the top of the stack is waiting to combine each time we append a new token. However, this doesn't handle /a|b*/ properly. The pattern is supposed to mean "one a or any number of b", but the check-and-combine strategy will turn it into the equivalent of /(a|b)*/.

A better (i.e., correct) solution is to leave some partially-completed tokens in the output and compress them later (). If our input is the pattern /a|b/, we can:

1. Append a Lit token for a.

2. When we see |, make that Lit token the left child of the Alt and append that without filling in the right child.

3. Append the Lit token for b.

4. After all tokens have been handled, look for partially-completed Alt tokens and make whatever comes after them their right child.

Again, this automatically handles patterns like /(ab)|c*|(de)/.

It's time to turn these ideas into code. The main structure of our parser is:

import assert from 'assert'

import tokenize from './tokenizer.js'

const parse = (text) => {
const result = []
const allTokens = tokenize(text)
for (let i = 0; i < allTokens.length; i += 1) {
const token = allTokens[i]
const last = i === allTokens.length - 1
handle(result, token, last)
}
return compress(result)
}

export default parseparser.js

We handle tokens case by case (with a few assertions to check that patterns are well formed):


const handle = (result, token, last) => {
if (token.kind === 'Lit') {
result.push(token)
} else if (token.kind === 'Start') {
assert(result.length === 0,
'Should not have start token after other tokens')
result.push(token)
} else if (token.kind === 'End') {
assert(last,
'Should not have end token before other tokens')
result.push(token)
} else if (token.kind === 'GroupStart') {
result.push(token)
} else if (token.kind === 'GroupEnd') {
result.push(groupEnd(result, token))
} else if (token.kind === 'Any') {
assert(result.length > 0,
No operand for '*' (location ${token.loc})) token.child = result.pop() result.push(token) } else if (token.kind === 'Alt') { assert(result.length > 0, No operand for '*' (location${token.loc}))
token.left = result.pop()
token.right = null
result.push(token)
} else {
assert(false, 'UNIMPLEMENTED')
}
}parser.js

When we find the ) that marks the end of a group, we take items from the end of the output list until we find the matching start and use them to create a group:


const groupEnd = (result, token) => {
const group = {
kind: 'Group',
loc: null,
end: token.loc,
children: []
}
while (true) {
assert(result.length > 0,
Unmatched end parenthesis (location ${token.loc})) const child = result.pop() if (child.kind === 'GroupStart') { group.loc = child.loc break } group.children.unshift(child) } return group }parser.js Finally, when we have finished with the input, we go through the output list one last time to fill in the right side of Alts:  const compress = (raw) => { const cooked = [] while (raw.length > 0) { const token = raw.pop() if (token.kind === 'Alt') { assert(cooked.length > 0, No right operand for alt (location${token.loc}))
token.right = cooked.shift()
}
cooked.unshift(token)
}
return cooked
}parser.js

Once again, it's not done until we've tested it:

import assert from 'assert'

import parse from '../parser.js'

describe('parses correctly', async () => {
it('parses the empty string', () => {
assert.deepStrictEqual(parse(''), [])
})

it('parses a single literal', () => {
assert.deepStrictEqual(parse('a'), [
{ kind: 'Lit', loc: 0, value: 'a' }
])
})

it('parses multiple literals', () => {
assert.deepStrictEqual(parse('ab'), [
{ kind: 'Lit', loc: 0, value: 'a' },
{ kind: 'Lit', loc: 1, value: 'b' }
])
})

it('parses alt of groups', () => {
assert.deepStrictEqual(parse('a|(bc)'), [
{
kind: 'Alt',
loc: 1,
left: { kind: 'Lit', loc: 0, value: 'a' },
right: {
kind: 'Group',
loc: 2,
end: 5,
children: [
{ kind: 'Lit', loc: 3, value: 'b' },
{ kind: 'Lit', loc: 4, value: 'c' }
]
}
}
])
})
})test/test-parser.js

> stjs@1.0.0 test /u/stjs
> mocha */test/test-*.js "-g" "parses correctly"

parses correctly
✓ parses the empty string
✓ parses a single literal
✓ parses multiple literals
✓ parses start anchors
✓ handles circumflex not at start
✓ parses end anchors
✓ parses circumflex not at start
✓ parses empty groups
✓ parses groups containing characters
✓ parses two groups containing characters
✓ parses any
✓ parses any of group
✓ parses alt
✓ parses alt of any
✓ parses alt of groups

15 passing (11ms)

parser-test.out

While our final parser is less than 90 lines of code, it is doing a lot of complex things. Compared to parsers for things like JSON and YAML, though, it is still very simple. If we have more operators with different precedences we should switch to the shunting-yard algorithm, and if we need to handle a language like JavaScript we should explore tools like ANTLR, which can generate a parser automatically given a description of the language to be parsed. As we said at the start, though, if our design requires us to write a parser we should try to come up with a better design. CSV, JSON, YAML, and other formats have their quirks, but at least they're broken the same way everywhere.

### The limits of computing

One of the most important theoretical results in computer science is that every formal language corresponds to a type of abstract machine and vice versa, and that some languages (or machines) are more or less powerful than others. For example, every regular expression corresponds to a finite state machine (FSM) like the one in . As powerful as FSMs are, they cannot match things like nested parentheses or HTML tags, and attempting to do so is a sin. If you add a stack to the system you can process a much richer set of languages, and if you add two stacks you have something equivalent to a Turing Machine that can do any conceivable computation. Conery2021 presents this idea and others for self-taught developers.

## Exercises

### Create objects

Modify the parser to return instances of classes derived from RegexBase.

### Escape characters

Modify the parser to handle escape characters, so that (for example) \* is interpreted as "a literal '*' character" and \\ is interpreted as "a literal backslash".

### Lazy matching

Modify the parser so that *? is interpreted as a single token meaning "lazy match zero or more".

### Character sets

Modify the parser so that expressions like [xyz] are interpreted to mean "match any one of the characters 'x', 'y', or 'z'".

### Back reference

Modify the tokenizer so that it recognizes \1, \2, and so on to mean "back reference". The number may contain any number of digits.

### Named groups

1. Modify the tokenizer to recognize named groups. For example, the named group /(?<triple>aaa)/ would create a named group called triple that matches exactly three consecutive occurrences of 'a'.

2. Write Mocha tests for your modified tokenizer. Does it handle nested named groups?

### Object streams

Write a parser that turns files of key-value pairs separated by blank lines into objects. For example, if the input is:

left: "left value"
first: 1

middle: "middle value"
second: 2

right: "right value"
third: 3


then the output will be:

[
{left: "left value", first: 1},
{middle: "middle value", second: 2},
{right: "right value", third: 3}
]


Keys are always upper- and lower-case characters; values may be strings in double quotes or unquoted numbers.

### Tokenize HTML

1. Write a tokenizer for a subset of HTML that consists of:

• Opening tags without attributes, such as <div> and <p>
• Closing tags, such as </p> and </div>
• Plain text between tags that does not contain '<' or '>' characters
2. Modify the tokenizer to handle key="value" attributes in opening tags.

3. Write Mocha tests for your tokenizer.

### The Shunting Yard Algorithm

1. Use the shunting-yard algorithm to implement a tokenizer for a simple subset of arithmetic that includes:

• single-letter variable names
• single-digit numbers
• the +, *, and ^ operators, where + has the lowest precedence and ^ has the highest
2. Write Mocha tests for your tokenizer.

### Handling errors

1. What does the regular expression tokenizer do with expressions that contain unmatched opening parentheses like /a(b/? What about expressions that contain unmatched closing parentheses like /ab)/?

2. Modify it so it produces a more useful error message.