Re: Why have a separate lexer instead of parsing 'all the way down'?

Newsgroups	comp.programming
Date	2018-07-30 09:02 -0700
References	<cf70d513-0ca4-4679-9bc9-6fc33a60e557@googlegroups.com> <pjk7rd$dd0$1@dont-email.me>
Message-ID	<6dcb2be5-e5d4-4324-bca6-cfe72f7094c2@googlegroups.com> (permalink)
Subject	Re: Why have a separate lexer instead of parsing 'all the way down'?
From	Chad <cdalten@gmail.com>

Show all headers | View raw

Sometimes it's easier to build a debugger when the lexer is separated. Especially if the program has to decorate the abstract syntax tree using keywords prior to being fed into an interpreter that in turn executes the debugger.

Back to comp.programming | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Why have a separate lexer instead of parsing 'all the way down'? luser droog <mijoryx@yahoo.com> - 2018-07-28 16:11 -0700
  Re: Why have a separate lexer instead of parsing 'all the way down'? "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> - 2018-07-29 10:06 +0200
  Re: Why have a separate lexer instead of parsing 'all the way down'? Richard Heathfield <rjh@cpax.org.uk> - 2018-07-29 12:19 +0100
    Re: Why have a separate lexer instead of parsing 'all the way down'? Chad <cdalten@gmail.com> - 2018-07-30 09:02 -0700

csiph-web