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

Groups > comp.lang.forth > #51414

Re: RfD Recognizer, 3rd version

Newsgroups comp.lang.forth
Date 2016-09-27 19:09 -0700
References (1 earlier) <a6a3672d-2e36-4085-93bf-fbf4cc3a7d0e@googlegroups.com> <87oa3a6jn2.fsf@jester.gateway.pace.com> <7cf7cab7-4593-48e7-a088-218458d61003@googlegroups.com> <87fuol7ups.fsf@jester.gateway.pace.com> <b9qdnb_VYP2QrXfKnZ2dnUU7-TfNnZ2d@supernews.com>
Message-ID <bb4789a1-e1c7-49cd-be30-dd1fbb79ebd6@googlegroups.com> (permalink)
Subject Re: RfD Recognizer, 3rd version
From trans <transfire@gmail.com>

Show all headers | View raw

On Tuesday, September 27, 2016 at 4:38:42 AM UTC-4, Andrew Haley wrote:
> Paul Rubin <no.email@nospam.invalid> wrote:
> > tabcomputing@gmail.com writes:
> >> Thanks, that helps. So it still goes word by word. But isn't that
> >> going to be rather slow? Every word has to run thru 1 to N functions
> >> to find a match, usually N. 
> > 
> > Usually 1.  The first thing is look up the word in the dictionary.  If
> > not, see if it's an integer literal, etc.  That's what the text
> > interpreter does now.
> 
> I think the proposal is to allow recognizers to be run before
> dictionary search.  The dictionary search itself can be a recognizer,
> and can appear anywhere in the recognizer stack.

In fact I realized today that a string recognizer that could handle spaces (e.g. `"foo bar"`, would *have* to come before the dictionary recognizer, otherwise things could turn into a hot mess., e.g. if someone defined a word `"foo`.

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

Thread

Re: RfD Recognizer, 3rd version trans <transfire@gmail.com> - 2016-09-26 20:33 -0700
  Re: RfD Recognizer, 3rd version Paul Rubin <no.email@nospam.invalid> - 2016-09-26 21:39 -0700
    Re: RfD Recognizer, 3rd version tabcomputing@gmail.com - 2016-09-26 22:45 -0700
      Re: RfD Recognizer, 3rd version Paul Rubin <no.email@nospam.invalid> - 2016-09-26 22:55 -0700
        Re: RfD Recognizer, 3rd version Andrew Haley <andrew29@littlepinkcloud.invalid> - 2016-09-27 03:38 -0500
          Re: RfD Recognizer, 3rd version anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2016-09-27 12:42 +0000
          Re: RfD Recognizer, 3rd version Bernd Paysan <bernd@net2o.de> - 2016-09-27 13:23 +0000
          Re: RfD Recognizer, 3rd version trans <transfire@gmail.com> - 2016-09-27 19:09 -0700
            Re: RfD Recognizer, 3rd version JennyB <jennybrien@googlemail.com> - 2016-09-28 00:07 -0700
              Re: RfD Recognizer, 3rd version anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2016-09-30 12:34 +0000
            Re: RfD Recognizer, 3rd version albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2016-09-28 10:03 +0200
              Re: RfD Recognizer, 3rd version ruvim.pinka@gmail.com - 2016-09-28 02:39 -0700
                Re: RfD Recognizer, 3rd version albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2016-09-28 13:22 +0200
            Re: RfD Recognizer, 3rd version anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2016-09-28 11:41 +0000
      Re: RfD Recognizer, 3rd version albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2016-09-27 15:15 +0200

csiph-web