From: anton@mips.complang.tuwien.ac.at   
      
   dxf writes:   
   >On 8/05/2024 2:07 am, Anton Ertl wrote:   
   >> If it is common practice, and you want to see it   
   >> standardized, make a proposal; documenting the common practice in   
   >> systems and programs would be useful to support such a proposal.   
   >   
   >It's my understanding the Technical Committee has responsibility for   
   >maintaining Standard Forth and keeping it relevant.   
      
   Apparently nobody inside the committee or outside thinks that "(.)"   
   etc. are sufficiently important to be added to the standard, otherwise   
   someone would have made a proposal for them, an option that is open to   
   everyone.   
      
   The committee is not a closed club, either, and we would love to have   
   more participation there, but the bar is somewhat higher, because   
   presence at two consecutive meetings is required (this requirement can   
   be lowered at the discretion of the committee).   
      
   >That ignores the use of number strings in applications. SwiftForth did   
   >the right thing in providing them upfront. From one of my apps:   
   >   
   >\ Save settings to file   
   >: !SETTINGS ( -- )   
   > s" [options]" write   
   > s" -s" write send.s @ (.) write   
   > s" -c" write char.s @ (.) write   
   > s" -d" write wspace @ (.) write   
   > cspace @ dup 3 <> and ?dup if   
   > [char] , writechr (.) write   
   > then   
   > s" -t" write tone @ (.) write   
   > s" -o" compress @ 0= and write   
   > s" -p" write punct @ (.) write   
   > s" -l" lsignal @ 0<> and write   
   > s" -u" write volume @ (.) write   
   > writecr ;   
      
   It seems to me that your system is missing a word like   
      
   'outfile-execute' ( ... xt file-id -- ... ) gforth-0.7 "outfile-execute"   
    execute xt with the output of 'type' etc. redirected to file-id.   
      
   With that word you could write !SETTINGS as:   
      
   \ Save settings to file   
   : .SETTINGS ( -- )   
    ." [options]"   
    ." -s" send.s @ .   
    ." -c" char.s @ .   
    ." -d" wspace @ .   
    cspace @ dup 3 <> and ?dup if   
    [char] , emit .   
    then   
    ." -t" tone @ .   
    ." -o" compress @ 0= and type   
    ." -p" punct @ .   
    ." -l" lsignal @ 0<> and type   
    ." -u" volume @ .   
    cr ;   
      
   : !settings ( -- )   
    ['] .settings dxf's-default-file @ outfile-execute ;   
      
   This allows you to test .SETTINGS interactively and eliminates the   
   need for words like WRITE, WRITECHR and WRITECR.   
      
   - 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 2023: https://euro.theforth.net/2023   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|