Re: Languages with optional spaces

Hans-Peter Diettrich <DrDiettrich1@netscape.net>
Sun, 1 Mar 2020 00:28:26 +0100

          From comp.compilers

Related articles
[5 earlier articles]
Re: Languages with optional spaces martin@gkc.org.uk (Martin Ward) (2020-02-25)
Re: Languages with optional spaces 493-878-3164@kylheku.com (Kaz Kylheku) (2020-02-26)
Re: Languages with optional spaces awanderin@gmail.com (awanderin) (2020-02-26)
Re: Languages with optional spaces drikosev@gmail.com (Ev. Drikos) (2020-02-28)
Re: Languages with optional spaces christopher.f.clark@compiler-resources.com (Christopher F Clark) (2020-02-29)
Re: Languages with optional spaces drikosev@gmail.com (Ev. Drikos) (2020-02-29)
Re: Languages with optional spaces DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2020-03-01)
Re: Languages with optional spaces christopher.f.clark@compiler-resources.com (Christopher F Clark) (2020-03-01)
Re: Languages with optional spaces drikosev@gmail.com (Ev. Drikos) (2020-03-01)
Re: Languages with optional spaces christopher.f.clark@compiler-resources.com (Christopher F Clark) (2020-03-02)
Re: Languages with optional spaces drikosev@gmail.com (Ev. Drikos) (2020-03-02)
Re: Languages with optional spaces gah4@u.washington.edu (2020-03-02)
Re: Languages with optional spaces drikosev@gmail.com (Ev. Drikos) (2020-03-12)
| List of all articles for this month |

From: Hans-Peter Diettrich <DrDiettrich1@netscape.net>
Newsgroups: comp.compilers
Date: Sun, 1 Mar 2020 00:28:26 +0100
Organization: Compilers Central
References: 20-02-015 20-02-017 20-02-033
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

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]


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.