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


Groups > comp.lang.forth > #55906

Re: bug in VFX --- IF does't work

From rickman <gnuarm@gmail.com>
Newsgroups comp.lang.forth
Subject Re: bug in VFX --- IF does't work
Date 2017-03-18 17:37 -0400
Organization A noiseless patient Spider
Message-ID <oak95d$sr4$1@dont-email.me> (permalink)
References <2e398151-3bb9-4827-8b25-2065117703f1@googlegroups.com> <551bd2e8.431024070@news.eternal-september.org> <c73bb02b-badf-4da0-968f-2068da15314b@googlegroups.com>

Show all headers | View raw


On 4/1/2015 3:33 PM, hughaguilar96@gmail.com wrote:
> On Wednesday, April 1, 2015 at 4:26:52 AM UTC-7, Stephen Pelc wrote:
>> On Tue, 31 Mar 2015 15:13:12 -0700 (PDT), hughaguilar96@gmail.com
>> wrote:
>>
>>> : my-if [ ' if ] literal execute ; immediate  ok : ttt ( flag --
>>> ) my-if ." true " else ." false " then ;=20 Err# -14 ERR: Attempt
>>> to interpret a compile only definition. -> : ttt ( flag -- )
>>> my-if ." true " else ." false " then ; ^ see my-if=20 MY-IF (is
>>> IMMEDIATE)=20 ( 004C7A80    E89B23F4FF )            CALL
>>> 00409E20        IF ( 004C7A85    C3 )                    NEXT, (
>>> 6 bytes, 2 instructions ) ok
>>
>> It works fine. You compiled MY-IF to use the interpretation
>> behaviour of IF. VFX compiled the interpretation behaviour of IF.
>> You ran MY-IF and got the interpretation behaviour of IF. What are
>> you complaining about?
>
> Well, you said "interpretation behavior" three times, so I felt
> inspired to look this up in the ANS-Forth document section on IF
> (6.1.1700): "Interpretation semantics for this word are undefined."
> You ask what I'm complaining about, but then your explanation comes
> to "undefined." That is funny! This is actually a familiar phrase, as
> I recently ran into the same thing in this thread:
> https://groups.google.com/forum/#!topic/comp.lang.forth/2OsjCUri9eY

This is simple enough that even I can understand it.

You exited compilation mode using [.  You ticked 'if'.  So what would 
you expect to get other than an execution token for the interpretation 
semantics of 'if'?

You complain that gForth doesn't return a token for a word that has no 
interpretation semantics and now you complain that VFX *does* return a 
token.


>> I have been saying for a couple of years now that the ANS
>> standard's definition of compilation and interpretation is
>> incomprehensible for mere mortals such as myself. Every time I
>> reread the standard on this topic, the more I believe that the
>> standard's description of compilation and interpretation needs a
>> complete rewrite.
>>
>> In essence, Forth is a language of simplicity. Complexity such as
>> an optimising compiler is hidden. However, we now have a standard
>> in which the classic Forth interpreter loop is broken according to
>> some. We need to fix this by going back to basics rather than
>> putting bandages on bad prose.
>
> I've been saying since 2009, which is more than a couple of years,
> that the solution is to define the language as a cross-compiler.

You continue to rant about how terrible ANS-Forth is... and also 
continue to pursue working with it.  I don't get why?  Do you like 
beating your head against the wall?  You won't learn how to use 
ANS-Forth.  Rather you insist on trying to bend it to your own will.

If you want something different, why don't you just write it?


> I wrote MFX in 1994/1995, and I figured it out on my own without
> doing any research on Forth cross-compilation.

So why are you here?

-- 

Rick C

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


Thread

Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2017-03-18 17:37 -0400
  Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2017-03-18 15:08 -0700
  Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2017-03-18 15:17 -0700
    Re: bug in VFX --- IF does't work Alex <alex@rivadpm.com> - 2017-03-18 22:22 +0000
      Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2017-03-18 19:47 -0400
        Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2017-03-18 17:06 -0700
          Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2017-03-18 20:58 -0400
          Re: bug in VFX --- IF does't work Alex <alex@rivadpm.com> - 2017-03-19 18:04 +0000
  Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-19 10:53 +0000
    Re: bug in VFX --- IF does't work Cecil Bayona <cbayona@cbayona.com> - 2017-03-19 12:57 -0500
      Re: bug in VFX --- IF does't work Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-19 13:39 -0500
      Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2017-03-19 14:48 -0700
        Re: bug in VFX --- IF does't work Alex <alex@rivadpm.com> - 2017-03-19 22:05 +0000
    Re: bug in VFX --- IF does't work Alex <alex@rivadpm.com> - 2017-03-19 17:57 +0000
    Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2017-03-19 12:18 -0700
    Re: bug in VFX --- IF does't work Bernd Paysan <bernd@net2o.de> - 2017-03-22 22:57 +0000
      Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2017-03-22 17:18 -0700
      Re: bug in VFX --- IF does't work Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-23 04:03 -0500
        Re: bug in VFX --- IF does't work albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-03-23 15:01 +0100
          Re: bug in VFX --- IF does't work peter.m.falth@gmail.com - 2017-03-23 07:12 -0700
            Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2017-03-29 20:31 -0700
          Re: bug in VFX --- IF does't work Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-23 10:22 -0500
            Re: bug in VFX --- IF does't work Bernd Paysan <bernd@net2o.de> - 2017-03-30 02:31 +0000
              Re: bug in VFX --- IF does't work Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-30 03:36 -0500
                Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-30 15:45 +0000
                Re: bug in VFX --- IF does't work Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-30 12:03 -0500
                Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2017-03-30 14:04 -0700
                Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-31 09:23 +0000
                Re: bug in VFX --- IF does't work Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-31 07:43 -0500
                Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-04-01 12:55 +0000
                Re: bug in VFX --- IF does't work Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-04-01 11:52 -0500
      Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-23 12:23 +0000
        Re: bug in VFX --- IF does't work Alex <alex@rivadpm.com> - 2017-03-23 15:57 +0000
          Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-23 17:38 +0000
            Re: bug in VFX --- IF does't work Alex <alex@rivadpm.com> - 2017-03-23 17:58 +0000
              Re: bug in VFX --- IF does't work Alex <alex@rivadpm.com> - 2017-03-23 19:16 +0000
              Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-24 09:52 +0000
        Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-23 18:26 +0000
        Re: bug in VFX --- IF does't work Bernd Paysan <bernd@net2o.de> - 2017-03-30 02:55 +0000
          Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2017-03-29 20:49 -0700
          Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2017-03-30 03:04 -0700
            Re: bug in VFX --- IF does't work Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-30 06:47 -0500
              Re: bug in VFX --- IF does't work Alex <alex@rivadpm.com> - 2017-03-30 12:56 +0100
                Re: bug in VFX --- IF does't work Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-30 09:41 -0500
              Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2017-03-30 13:59 -0700
              Re: bug in VFX --- IF does't work Bernd Paysan <bernd@net2o.de> - 2017-05-01 01:33 +0000
                Re: bug in VFX --- IF does't work "Elizabeth D. Rather" <erather@forth.com> - 2017-04-30 15:50 -1000
                Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2017-04-30 19:34 -0700
                Re: bug in VFX --- IF does't work albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-05-01 23:53 +0200
                Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2017-05-01 18:54 -0700
                Re: bug in VFX --- IF does't work Bernd Paysan <bernd@net2o.de> - 2017-05-02 15:01 +0000
                Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2017-05-02 11:30 -0700
                Re: bug in VFX --- IF does't work Cecil Bayona <cbayona@cbayona.com> - 2017-05-02 13:36 -0500
                Re: bug in VFX --- IF does't work Bernd Paysan <bernd@net2o.de> - 2017-05-02 22:57 +0000
          Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-31 09:45 +0000
            Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2017-03-31 20:09 -0700

csiph-web