Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.forth > #58954

Re: "Recognizing" a parser generator (and a compiler compiler)

Show all headers | View raw

In article <5187a636-8855-4b7a-859f-9f5a06574a45@googlegroups.com>,
 <mhx@iae.nl> wrote:
>On Tuesday, May 9, 2017 at 6:07:36 AM UTC+2, Joel Rees wrote:
>> On Monday, May 8, 2017 at 5:41:30 PM UTC+9, Alex wrote:
>> > On 5/8/2017 03:29, Joel Rees wrote:
>> > > What am I missing, Alex?
>> >
>[..]
>> Have you ever used lex and yacc? Or even worked on a program that
>> is constructed using them?
>
>Currently I am one of the NGSPICE maintainers. This open source
>SPICE program uses lex and yacc to build the interpreter
>for its simulator engine.
>
>The lex/yacc tools make for *very* difficult reading, and the
>make process (2000 files on windows/linux) is true horror.
>I am not sure if lex/yacc are helping or just obstructing.
>They are not used consistently and the results are so-so.
>
>There are many places in (NG)SPICE where Forth would
>be a dream to work with. E.g. the behavioral sources
>build parse-trees that are interpreted (!) by the
>simulation engine. This is where *a lot* of run-time
>is spend, especially for the kind of circuits I am
>interested in. On-the-fly compilation (i.e. Forth)
>would be vastly more efficient. I probably should
>say "will be" :-)

What are the chance for creating a hybrid system?
Not replacing the whole system, but replacing a part
where Forth would be better, then maybe expanding it?
>
>-marcel
-- 
Albert van der Horst, UTRECHT,THE NETHERLANDS
Economic growth -- being exponential -- ultimately falters.
albert@spe&ar&c.xs4all.nl &=n http://home.hccnet.nl/a.w.m.van.der.horst

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

Thread

"Recognizing" a parser generator (and a compiler compiler) Joel Rees <joel.rees@gmail.com> - 2017-05-07 19:29 -0700
  Re: "Recognizing" a parser generator (and a compiler compiler) hughaguilar96@gmail.com - 2017-05-07 21:57 -0700
    Re: "Recognizing" a parser generator (and a compiler compiler) Alex <alex@rivadpm.com> - 2017-05-08 09:55 +0100
  Re: "Recognizing" a parser generator (and a compiler compiler) Alex <alex@rivadpm.com> - 2017-05-08 09:41 +0100
    Re: "Recognizing" a parser generator (and a compiler compiler) Joel Rees <joel.rees@gmail.com> - 2017-05-08 21:07 -0700
      Re: "Recognizing" a parser generator (and a compiler compiler) Alex <alex@rivadpm.com> - 2017-05-09 07:50 +0100
        Re: "Recognizing" a parser generator (and a compiler compiler) "Elizabeth D. Rather" <erather@forth.com> - 2017-05-08 21:39 -1000
          Re: "Recognizing" a parser generator (and a compiler compiler) "HAA" <someone@microsoft.com> - 2017-05-10 15:27 +1000
            Re: "Recognizing" a parser generator (and a compiler compiler) Alex <alex@rivadpm.com> - 2017-05-10 08:21 +0100
              Re: "Recognizing" a parser generator (and a compiler compiler) "HAA" <someone@microsoft.com> - 2017-05-10 18:15 +1000
          Re: "Recognizing" a parser generator (and a compiler compiler) Joel Rees <joel.rees@gmail.com> - 2017-05-10 00:53 -0700
            Re: "Recognizing" a parser generator (and a compiler compiler) Alex <alex@rivadpm.com> - 2017-05-10 08:59 +0100
      Re: "Recognizing" a parser generator (and a compiler compiler) mhx@iae.nl - 2017-05-10 02:52 -0700
        Re: "Recognizing" a parser generator (and a compiler compiler) albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-05-10 11:59 +0200
          Re: "Recognizing" a parser generator (and a compiler compiler) Joel Rees <joel.rees@gmail.com> - 2017-05-10 05:46 -0700
          Re: "Recognizing" a parser generator (and a compiler compiler) mhx@iae.nl - 2017-05-10 05:48 -0700

csiph-web