Re: Parsing a file name with spaces

From	anton@mips.complang.tuwien.ac.at (Anton Ertl)
Newsgroups	comp.lang.forth
Subject	Re: Parsing a file name with spaces
Date	2026-04-01 07:54 +0000
Organization	Institut fuer Computersprachen, Technische Universitaet Wien
Message-ID	<2026Apr1.095400@mips.complang.tuwien.ac.at> (permalink)
References	(8 earlier) <10qf8nr$2vaat$1@dont-email.me> <2026Mar31.095456@mips.complang.tuwien.ac.at> <10qg65r$380qk$1@dont-email.me> <2026Mar31.123237@mips.complang.tuwien.ac.at> <10qgp41$3ejgv$2@dont-email.me>

Show all headers | View raw

Krishna Myneni <krishna.myneni@ccreweb.org> writes:
>On 3/31/26 5:32 AM, Anton Ertl wrote:
>> Krishna Myneni <krishna.myneni@ccreweb.org> writes:
>>> INCLUDED is not a parsing form, which is needed in some use cases.
>> 
>> In which use cases?
>> 
>
>In cases such as the TAIL example I gave earlier.

I doubt that INCLUDE is a factor of TAIL, so how INCLUDE parses its
file name is independent of how TAIL gets its file name.

>For those case where 
>you want to provide a Forth word to the user in the form
>
><wordname> <file1> <file2> ...

Ok, you "want", probably because you think it's more convenient for
the user, i.e., no technical reason.

You have the choices:

1) Pass each file names as c-addr u on the stack.  Advantages:

   a) This word can deal with all kinds of file names.

   b) The user can use whatever is appropriate for the file name: S"
      for a file name with only blanks; or S\" for a file name that
      contain " or control characters.  The user can use the
      appropriate way for each file name.

   c) The word is more flexible for use as factor in other words.

2) Write a parsing word that uses PARSE-NAME.  Advantages:

   a) Easy to implement.

   b) fits with the usual white-space-delimited Forth syntax

   Disadvantage: Cannot deal with file names containing white space.

3) Write a parsing word that uses '"' PARSE.

   Advantage: Can deal with file names containing white space.

   Disadvantage: Cannot deal with file names containing " or control
   characters.

4) Write a parsing word that uses ['] S\" EXECUTE.

   Advantage: Can deal with all kinds of file names.

   Disadvantage: The user needs to escape \ (supported by 2 and 3) and
   " (supported by 2), and to use appropriate sequences for control
   characters (supported by neither 2 nor 3).

If you want to provide parsing words to the user, for convenience and
completeness you might want to provide 2, 3, and 4, and implement 1 as
common factor, and document at least 2-4.  But is the result really
more convenient for the user than just providing 1?

- anton
-- 
M. Anton Ertl  http://www.complang.tuwien.ac.at/anton/home.html
comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html
     New standard: https://forth-standard.org/
EuroForth 2025 proceedings: http://www.euroforth.org/ef25/papers/

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

Thread

Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-24 08:51 -0500
  Re: Parsing a file name with spaces peter <peter.noreply@tin.it> - 2026-03-24 15:24 +0100
  Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-03-25 01:28 +1100
    Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-03-25 21:24 +1100
      Re: Parsing a file name with spaces albert@spenarnc.xs4all.nl - 2026-03-25 14:57 +0100
  Re: Parsing a file name with spaces Stephen Pelc <stephen@vfxforth.com> - 2026-03-24 15:55 +0000
    Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-25 10:05 -0500
      Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-03-25 16:56 +0000
        Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-25 15:22 -0500
          Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-03-28 12:02 +1100
            Re: Parsing a file name with spaces albert@spenarnc.xs4all.nl - 2026-03-28 08:54 +0100
              Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-03-28 19:37 +1100
                Re: Parsing a file name with spaces sjack@dontemail.me (sjack) - 2026-03-28 15:10 +0000
          Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-03-28 18:59 +0000
            Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-03-29 11:11 +1100
              Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-03-29 09:24 +0000
                Re: Parsing a file name with spaces albert@spenarnc.xs4all.nl - 2026-03-29 13:03 +0200
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-03-29 22:07 +1100
                Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-03-29 16:08 +0000
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-03-30 09:34 +1100
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-03-31 09:18 +1100
                Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-30 20:41 -0500
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-03-31 14:14 +1100
                Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-03-31 07:36 +0000
                Re: Parsing a file name with spaces albert@spenarnc.xs4all.nl - 2026-03-31 14:03 +0200
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-01 12:22 +1100
                Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-04-01 08:22 +0000
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-01 20:06 +1100
                Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-04-02 06:05 +0000
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-02 18:09 +1100
                Re: Parsing a file name with spaces albert@spenarnc.xs4all.nl - 2026-04-02 13:54 +0200
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-03 11:57 +1100
                Re: Parsing a file name with spaces albert@spenarnc.xs4all.nl - 2026-04-03 11:44 +0200
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-04 00:23 +1100
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-05 10:55 +1000
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-05 11:50 +1000
                Re: Parsing a file name with spaces albert@spenarnc.xs4all.nl - 2026-04-01 12:25 +0200
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-02 00:07 +1100
                Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-03-31 07:54 +0000
                Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-31 05:03 -0500
                Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-03-31 10:32 +0000
                Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-31 10:26 -0500
                Re: Parsing a file name with spaces albert@spenarnc.xs4all.nl - 2026-04-01 00:19 +0200
                Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-31 18:04 -0500
                Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-04-01 07:54 +0000
                Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-04-01 06:23 -0500
                Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-04-02 08:34 +0000
                Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-04-02 07:18 -0500
                Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-04-02 14:43 +0000
                Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-04-02 20:52 -0500
                Re: Parsing a file name with spaces albert@spenarnc.xs4all.nl - 2026-04-03 11:40 +0200
                Re: Parsing a file name with spaces sjack@dontemail.me (sjack) - 2026-04-04 06:21 +0000
                Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-04-04 08:00 -0500
                Re: Parsing a file name with spaces sjack@dontemail.me (sjack) - 2026-04-04 22:01 +0000
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-07 10:23 +1000
                Re: Parsing a file name with spaces sjack@dontemail.me (sjack) - 2026-04-07 14:26 +0000
                Re: Parsing a file name with spaces sjack@dontemail.me (sjack) - 2026-04-07 15:05 +0000
                Re: Parsing a file name with spaces sjack@dontemail.me (sjack) - 2026-04-07 17:09 +0000
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-08 12:25 +1000
                Re: Parsing a file name with spaces Stephen Pelc <stephen@vfxforth.com> - 2026-04-09 10:22 +0000
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-01 19:13 +1100
                Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-04-02 05:55 +0000
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-02 17:44 +1100
                Re: Parsing a file name with spaces albert@spenarnc.xs4all.nl - 2026-03-31 13:41 +0200
                Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-31 10:18 -0500
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-01 11:28 +1100
                Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-04-01 08:17 +0000
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-01 19:42 +1100
                Re: Parsing a file name with spaces albert@spenarnc.xs4all.nl - 2026-04-01 12:13 +0200
                Re: Parsing a file name with spaces Gerry Jackson <do-not-use@swldwa.uk> - 2026-04-01 19:43 +0100
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-02 12:18 +1100
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-02 12:43 +1100
                Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-04-02 09:07 +0000
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-02 21:50 +1100
                Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-04-02 09:11 +0000
                Re: Parsing a file name with spaces Hans Bezemer <the.beez.speaks@gmail.com> - 2026-04-12 19:37 +0200
                Re: Parsing a file name with spaces Hans Bezemer <the.beez.speaks@gmail.com> - 2026-04-12 19:44 +0200
                Re: Parsing a file name with spaces dxf <dxforth@gmail.com> - 2026-04-13 11:05 +1000
                Re: Parsing a file name with spaces Hans Bezemer <the.beez.speaks@gmail.com> - 2026-04-14 14:45 +0200
                Re: Parsing a file name with spaces Hans Bezemer <the.beez.speaks@gmail.com> - 2026-04-15 15:51 +0200
  Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-03-24 17:58 +0000
    Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-24 13:41 -0500
      Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-03-24 20:40 +0000
        Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-24 20:26 -0500
  Re: Parsing a file name with spaces albert@spenarnc.xs4all.nl - 2026-03-25 10:37 +0100
    Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-25 05:13 -0500
    Re: Parsing a file name with spaces Bigtreeman <treecolin@gmail.com> - 2026-03-26 09:16 +1000
      Re: Parsing a file name with spaces Krishna Myneni <krishna.myneni@ccreweb.org> - 2026-03-25 20:57 -0500
      Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-03-28 19:14 +0000
        Re: Parsing a file name with spaces Bigtreeman <treecolin@gmail.com> - 2026-03-29 12:22 +1000
          Re: Parsing a file name with spaces Paul Rubin <no.email@nospam.invalid> - 2026-03-28 20:55 -0700
            Re: Parsing a file name with spaces Bigtreeman <treecolin@gmail.com> - 2026-03-29 17:00 +1000
              Re: Parsing a file name with spaces Paul Rubin <no.email@nospam.invalid> - 2026-03-29 19:05 -0700
                Re: Parsing a file name with spaces Bigtreeman <treecolin@gmail.com> - 2026-03-30 21:58 +1000
            Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-03-29 09:52 +0000
          Re: Parsing a file name with spaces anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2026-03-29 09:32 +0000
            Re: Parsing a file name with spaces Bigtreeman <treecolin@gmail.com> - 2026-03-30 22:10 +1000
  Re: Parsing a file name with spaces Hans Bezemer <the.beez.speaks@gmail.com> - 2026-03-29 13:22 +0200

csiph-web