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

Groups > comp.lang.forth > #29026

Re: RfD: Interpret S\" (Version 2)

Show all headers | View raw

Andrew Haley wrote:
> We do, but two is so aribtrary that IMO it needs better justification
> than that's what RENAME-FILE needs.  Is it really a common case that
> you use Forth interactively to rename a file like this?

Let's try to be logical: The file wordset specifies interactive S" to allow 
the file words to be used interactively.  The one word with two strings as 
input is in the file wordset.  If you deduce S"'s capabilities from the use 
case (file words), you need to support RENAME-FILE.  Is this a frequently 
used case?  Probably not.  The only case I've ever used RENAME-FILE in Forth 
is in editors, where you write your new file as <name>+, and then rename the 
old file to <name>~ and the new file to <name>.  Ok, well, maybe I've used 
RENAME-FILE on some systems where the obnoxious file manager didn't allow 
some names, which the file system itself allowed, and then Forth came to 
rescue (e.g. Android).

Whether there should be a buffer in all cases is also a bit questionable: 
The way small systems deal with s" is to define the interactive part as

'"' parse

and leave the string in the input buffer.  This allows to have as many 
strings as you want, granted they fit into a single line (together with the 
operation), which is usually limited to 80 characters.

-- 
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

RfD: Interpret S\" (Version 2) "Peter Knaggs" <pjk@bcs.org.uk> - 2014-03-11 11:18 +0000
  Re: RfD: Interpret S\" (Version 2) "Alex McDonald" <blog@rivadpm.com> - 2014-03-11 18:36 +0000
    Re: RfD: Interpret S\" (Version 2) Bernd Paysan <bernd.paysan@gmx.de> - 2014-03-11 21:32 +0100
      Re: RfD: Interpret S\" (Version 2) "Alex McDonald" <blog@rivadpm.com> - 2014-03-11 22:38 +0000
        Re: RfD: Interpret S\" (Version 2) Bernd Paysan <bernd.paysan@gmx.de> - 2014-03-12 13:02 +0100
      Re: RfD: Interpret S\" (Version 2) Andrew Haley <andrew29@littlepinkcloud.invalid> - 2014-03-12 04:41 -0500
        Re: RfD: Interpret S\" (Version 2) Bernd Paysan <bernd.paysan@gmx.de> - 2014-03-12 13:16 +0100
    Re: RfD: Interpret S\" (Version 2) Mark Wills <markwills1970@gmail.com> - 2014-03-12 04:33 -0700
      Re: RfD: Interpret S\" (Version 2) Bernd Paysan <bernd.paysan@gmx.de> - 2014-03-12 12:51 +0100
        Re: RfD: Interpret S\" (Version 2) Mark Wills <markwills1970@gmail.com> - 2014-03-12 06:25 -0700
          Re: RfD: Interpret S\" (Version 2) Coos Haak <chforth@hccnet.nl> - 2014-03-12 15:59 +0100
            Re: RfD: Interpret S\" (Version 2) Bernd Paysan <bernd.paysan@gmx.de> - 2014-03-12 19:43 +0100
          Re: RfD: Interpret S\" (Version 2) "Peter Knaggs" <pjk@bcs.org.uk> - 2014-03-13 18:55 +0000

csiph-web