Path: csiph.com!xmission!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Hans-Peter Diettrich Newsgroups: comp.compilers Subject: Re: Languages with optional spaces Date: Sun, 1 Mar 2020 00:28:26 +0100 Organization: Compilers Central Lines: 19 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <20-03-001@comp.compilers> References: <20-02-015@comp.compilers> <20-02-017@comp.compilers> <20-02-033@comp.compilers> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="53462"; mail-complaints-to="abuse@iecc.com" Keywords: parse, Basic, comment Posted-Date: 01 Mar 2020 12:48:28 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:2472 Am 29.02.2020 um 10:48 schrieb Christopher F Clark: > With a GLR parser (or something equivalent in power, e.g. an Earley > parser or CYK) and a lexer that returns all possible sets of > tokenizations one can find all the relevant parse trees and then see > if only 1 makes semantic sense. I wonder how those old coders could fit all that into about 4 KB ROM for their BASIC interpreter ;-) Isn't there a better solution nowadays than taking a sledgehammer to crack a nut? The reconstruction of the proper original syntax requires to disassemble the original code, so nothings hinders one from implementing just that code on new hardware. DoDi [I suppose it depends on whether you want to understand what the old 6502 code did, or just run it. I'm also not sure I want to emulate whatever passed for an arithmetic package on those machines. -John]