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


Groups > comp.lang.forth > #29493

Re: EXECUTE-PARSING (was: Which input to use?)

From Bernd Paysan <bernd.paysan@gmx.de>
Newsgroups comp.lang.forth
Subject Re: EXECUTE-PARSING (was: Which input to use?)
Date 2014-04-09 18:54 +0200
Organization 1&1 Internet AG
Message-ID <li3tva$svo$1@online.de> (permalink)
References <lhrndd$2pa$1@speranza.aioe.org> <2014Apr7.194501@mips.complang.tuwien.ac.at> <PbGdnRjos59ALd7OnZ2dnUVZ_rmdnZ2d@supernews.com> <2014Apr9.171309@mips.complang.tuwien.ac.at>

Show all headers | View raw


Anton Ertl wrote:
> You can interpret the name EXECUTE-PARSING as "EXECUTE, parsing the
> passed-in string" or just as "execute a parsing word".  I know that
> won't help Andrew, because his problem is that the name contains a
> hyphen:-).

We have a growing number of words which take an xt and execute it (higher 
order functions), and this is just one of them.  Therefore, we should think 
about a convention how to mark higher order functions; typical for Forth 
would be a pre- or postfix character which indicates that we execute 
something.  Just like <foo>@ or <foo>! indicate get and set, and <foo>? 
indicates a test.  Suggestions?  From C++'s templates, I would suggest using 
< and > around the name indicating that this takes an xt and is a sort-of 
template for doing things.

Another possibility is to use 'ing' as suffix, so PARSING is already a hint 
that this will take an xt for parsing.  I.e.

: :name ( addr u -- ) ['] : parsing ;

or

: :name ( addr u -- ) ['] : <parsing> ;

What looks better?

-- 
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://bernd-paysan.de/

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


Thread

Which input to use? Lauri Alanko <la@iki.fi> - 2014-04-06 14:13 +0000
  Re: Which input to use? mhx@iae.nl - 2014-04-06 07:59 -0700
    Re: Which input to use? "Elizabeth D. Rather" <erather@forth.com> - 2014-04-06 08:26 -1000
      Re: Which input to use? hughaguilar96@yahoo.com - 2014-04-19 19:48 -0700
        Re: Which input to use? "Alex McDonald" <blog@rivadpm.com> - 2014-04-21 02:09 +0100
          Re: Which input to use? "Rod Pemberton" <dont_use_email@xnothavet.cqm> - 2014-04-21 04:01 -0400
  Re: Which input to use? hughaguilar96@yahoo.com - 2014-04-06 23:16 -0700
  Re: Which input to use? albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-04-07 10:44 +0000
  Re: Which input to use? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-04-07 17:45 +0000
    Re: Which input to use? mhx@iae.nl - 2014-04-07 12:09 -0700
      Re: Which input to use? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-04-08 16:11 +0000
        Re: Which input to use? mhx@iae.nl - 2014-04-08 13:05 -0700
    Re: Which input to use? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2014-04-08 03:18 -0500
      Re: Which input to use? albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-04-08 10:49 +0000
        Re: Which input to use? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-04-09 16:07 +0000
          Re: Which input to use? albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-04-10 01:36 +0000
            Re: Which input to use? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-04-11 17:59 +0000
      Re: Which input to use? "Alex McDonald" <blog@rivadpm.com> - 2014-04-08 12:28 +0100
      Re: Which input to use? hughaguilar96@yahoo.com - 2014-04-08 21:03 -0700
        Re: Which input to use? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2014-04-09 03:14 -0500
      EXECUTE-PARSING (was: Which input to use?) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-04-09 15:13 +0000
        Re: EXECUTE-PARSING (was: Which input to use?) Bernd Paysan <bernd.paysan@gmx.de> - 2014-04-09 18:54 +0200
          Re: EXECUTE-PARSING (was: Which input to use?) Alexander Skobelev <al.skobelev@gmail.com> - 2014-04-09 22:44 -0700

csiph-web