Path: csiph.com!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder1.iad1.usenetexpress.com!216.166.98.84.MISMATCH!border1.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Hans-Peter Diettrich Newsgroups: comp.compilers Subject: Re: some guideline to lexer or parser Date: Tue, 28 Feb 2017 11:25:30 +0100 Organization: Compilers Central Lines: 14 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <17-03-001@comp.compilers> References: <17-02-005@comp.compilers> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: miucha.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="17511"; mail-complaints-to="abuse@iecc.com" Keywords: lex Posted-Date: 01 Mar 2017 20:21:42 EST X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:1822 Am 27.02.2017 um 05:53 schrieb chano: > is there any guideline document on simple lexer or parser on the internet? > I try to build routine to parse simple < data, data, data > format and I > find it it's no easy task Are you interested in theory or practice? In practice almost every programming language offers means for string handling, so that you can read a line of characters, or characters delimited by < and >. Then find the , in the string, and convert the characters in between. DoDi