SUBLEQ Compilation Routine is Coupled to Entry Point

[joebobmiles]

I'd like to make the SUBLEQ assembler embeddable, but that means it has be decoupled from the entry point. Right now the entry point is responsible for linking tokenization/lexing, parsing, and code generation (in fact, the entry point is responsible for performing code generation). This means that the app in which the assembler is embedded has to perform the same composition of operations.

To make the SUBLEQ assembler easier to embed, I'd like to create a SUBLEQ namespace and implement a single assemble() or compile() function that accepts string input and outputs an array of numbers (addresses).