On Wed, Sep 1, 2010 at 2:31 AM, Joel Goldstick <
joel.goldst...@columbuswebmakers.com> wrote:
> pyt...@bdurham.com wrote:
>
>> I'm parsing a simple, domain specific scripting language that has
>> commands like the following: *page, *title, *text, *footer, etc.
>> There are about 100 of these '*' c
Joel Goldstick writes:
> pyt...@bdurham.com wrote:
>> I'm parsing a simple, domain specific scripting language that has
>> commands like the following: *page, *title, *text, *footer, etc.
>> There are about 100 of these '*' commands. When we see a command
>> that we don't recognize, I would like
pyt...@bdurham.com wrote:
I'm parsing a simple, domain specific scripting language that has
commands like the following: *page, *title, *text, *footer, etc.
There are about 100 of these '*' commands. When we see a command
that we don't recognize, I would like to find the closest match
possible (f
On Tue, Aug 31, 2010 at 9:12 PM, wrote:
> I'm parsing a simple, domain specific scripting language that has commands
> like the following: *page, *title, *text, *footer, etc. There are about 100
> of these '*' commands. When we see a command that we don't recognize, I
> would like to find the clo
I'm parsing a simple, domain specific scripting language that has
commands like the following: *page, *title, *text, *footer, etc.
There are about 100 of these '*' commands. When we see a command
that we don't recognize, I would like to find the closest match
possible (from a list of all legal comm
