|
|
Up |
|
|
  |
Author: Bruce McFarlingBruce McFarling Date: Mar 11, 2008 10:49
Reading the Forth-94 draft proposal, it reads as if the SEARCH words
are supposed to provide a general foundation for building a wordlist
management system.
However, it does not seem that the capability of FORTH in SEARCH EXT
can necessarily be duplicated.
-1 SET-ORDER
and you are faced with whatever the system thinks is a minimal search-
order, with FORTH-WORDLIST and SET-ORDER is guaranteed to to be
available.
But you cannot necessarily *use* SET-ORDER to *bring* FORTH-WORDLIST
into the search order.
That is, (1) SET-ORDER needs a set of wordlists and a count.
(2) The only wordlist you can guarantee that you know about is FORTH-
WORDLIST
And (3) ``FORTH-WORDLIST 1 SET-ORDER'' is not guaranteed to work.
FORTH-WORDLIST has to provide the FORTH core when replacing the top of
the search order stack, but a system is not required to function with
nothing but FORTH-WORDLIST on the search-order stack. It is within its
rights to trap that as an error and abort.
|
| Show full article (2.78Kb) |
|
| | 10 Comments |
|
  |
Author: Josh GramsJosh Grams Date: Mar 11, 2008 14:11
Bruce McFarling netscape.net> wrote:
>
> But you cannot necessarily *use* SET-ORDER to *bring* FORTH-WORDLIST
> into the search order.
>
> That is, (1) SET-ORDER needs a set of wordlists and a count.
>
> (2) The only wordlist you can guarantee that you know about is FORTH-
> WORDLIST
>
> And (3) ``FORTH-WORDLIST 1 SET-ORDER'' is not guaranteed to work.
>
> FORTH-WORDLIST has to provide the FORTH core when replacing the top of
> the search order stack, but a system is not required to function with
> nothing but FORTH-WORDLIST on the search-order stack. It is within its
> rights to trap that as an error and abort.
|
| Show full article (1.32Kb) |
|
| | no comments |
|
  |
Author: Bruce McFarlingBruce McFarling Date: Mar 11, 2008 14:32
On Mar 11, 5:11 pm, Josh Grams qualdan.com> wrote:
> How did you get to that conclusion? A.16 does say that some systems
> need pseudo-wordlists in the search order to be able to understand
> numeric literals, but you don't need numeric literals to define FORTH
> or
> ALSO. So...I may be wrong, but I don't think that a standard system
> should treat FORTH-WORDLIST 1 SET-ORDER as an error.
First, I ran it, and it was an error. Then I opened the dpANS pdf and
read the standard SEARCH words.
There is nothing in the specification of FORTH-WORDLIST or of SET-
ORDER that explicitly requires ``FORTH-WORDLIST 1 SET-ORDER'' to
function as I had expected, and FORTH-WORDLIST and SET-ORDER are the
only words required to be present when you:
``-1 SET-ORDER''.
That's how I reached that conclusion.
A.16 is probably why I expected it would work, but its not part of
specification. If that was the intention, Forth200x could make that
intention explicit.
|
| Show full article (1.54Kb) |
| no comments |
|
  |
Author: Josh GramsJosh Grams Date: Mar 12, 2008 05:02
Bruce McFarling netscape.net> wrote:
> On Mar 11, 5:11 pm, Josh Grams qualdan.com> wrote:
>
>> How did you get to that conclusion? I may be wrong, but
>> I don't think that a standard system should treat
>> FORTH-WORDLIST 1 SET-ORDER as an error.
>
> First, I ran it, and it was an error.
Can I ask what Forth this is?
> There is nothing in the specification of FORTH-WORDLIST or of
> SET-ORDER that explicitly requires ``FORTH-WORDLIST 1
> SET-ORDER'' to function as I had expected...
I'd be inclined to take a less-inclusive view and say that since
the specification of SET-ORDER doesn't explicitly say that an
implementation may reject arbitrary search orders, or that you
have to base your search orders on an existing one instead of
passing whatever you want, that the behaviour you're seeing is
non-standard. But it doesn't really matter, since you want to
port to that system anyway...
|
| Show full article (1.70Kb) |
| no comments |
|
  |
Author: Bruce McFarlingBruce McFarling Date: Mar 12, 2008 08:30
On Mar 12, 8:02 am, Josh Grams qualdan.com> wrote:
> Bruce McFarling netscape.net> wrote:
>> On Mar 11, 5:11 pm, Josh Grams qualdan.com> wrote:
>>> How did you get to that conclusion? I may be wrong, but
>>> I don't think that a standard system should treat
>>> FORTH-WORDLIST 1 SET-ORDER as an error.
>> First, I ran it, and it was an error.
> Can I ask what Forth this is?
gforth 6.2
>> There is nothing in the specification of FORTH-WORDLIST or of
>> SET-ORDER that explicitly requires ``FORTH-WORDLIST 1
>> SET-ORDER'' to function as I had expected...
> I'd be inclined to take a less-inclusive view and say that since
> the specification of SET-ORDER doesn't explicitly say that an
> implementation may reject arbitrary search orders, or that you
> have to base your search orders on an existing one instead of
> passing whatever you want, that the behaviour you're seeing is
> non-standard. But it doesn't really matter, since you want to
> port to that system anyway...
|
| Show full article (2.95Kb) |
| no comments |
|
  |
Author: Neal BridgesNeal Bridges Date: Mar 12, 2008 09:09
On Mar 12, 11:30 am, Bruce McFarling netscape.net> wrote:
[snip]
> gforth has two wordlists in its search order when ONLY FORTH is
> executed ROOT and FORTH-WORDLIST. I haven't re-read the documentation
> to find out why (why is not an issue here, just whether) ... but it
> throws an error on ``FORTH-WORDLIST 1 SET-ORDER''.
Not here:
Gforth 0.6.2, Copyright (C) 1995-2003 Free Software Foundation, Inc.
Gforth comes with ABSOLUTELY NO WARRANTY; for details type `license'
Type `bye' to exit
-1 set-order ok
order Root Root Forth ok
forth-wordlist 1 set-order ok
order Forth Forth ok
|
| |
| no comments |
|
  |
Author: Bruce McFarlingBruce McFarling Date: Mar 12, 2008 10:07
On Mar 12, 12:09 pm, Neal Bridges gmail.com> wrote:
> On Mar 12, 11:30 am, Bruce McFarling netscape.net> wrote:
> [snip]
>
>> gforth has two wordlists in its search order when ONLY FORTH is
>> executed ROOT and FORTH-WORDLIST. I haven't re-read the documentation
>> to find out why (why is not an issue here, just whether) ... but it
>> throws an error on ``FORTH-WORDLIST 1 SET-ORDER''.
>
> Not here:
>
> Gforth 0.6.2, Copyright (C) 1995-2003 Free Software Foundation, Inc.
> Gforth comes with ABSOLUTELY NO WARRANTY; for details type `license'
> Type `bye' to exit
> -1 set-order ok
> order Root Root Forth ok
> forth-wordlist 1 set-order ok
> order Forth Forth ok
|
| Show full article (1.19Kb) |
| no comments |
|
  |
Author: m_l_g3m_l_g3 Date: Mar 12, 2008 10:30
On Mar 12, 7:09 pm, Neal Bridges gmail.com> wrote:
> On Mar 12, 11:30 am, Bruce McFarling netscape.net> wrote:
> [snip]
>
>> gforth has two wordlists in its search order when ONLY FORTH is
>> executed ROOT and FORTH-WORDLIST. I haven't re-read the documentation
>> to find out why (why is not an issue here, just whether) ... but it
>> throws an error on ``FORTH-WORDLIST 1 SET-ORDER''.
>
> Not here:
>
> Gforth 0.6.2, Copyright (C) 1995-2003 Free Software Foundation, Inc.
> Gforth comes with ABSOLUTELY NO WARRANTY; for details type `license'
> Type `bye' to exit
> -1 set-order ok
> order Root Root Forth ok
> forth-wordlist 1 set-order ok
> order Forth Forth ok
>
|
| Show full article (1.35Kb) |
| no comments |
|
  |
Author: Anton ErtlAnton Ertl Date: Mar 13, 2008 04:07
Bruce McFarling netscape.net> writes:
>On Mar 12, 8:02 am, Josh Grams qualdan.com> wrote:
>> Bruce McFarling netscape.net> wrote:
>>> On Mar 11, 5:11 pm, Josh Grams qualdan.com> wrote:
>
>>>> How did you get to that conclusion? I may be wrong, but
>>>> I don't think that a standard system should treat
>>>> FORTH-WORDLIST 1 SET-ORDER as an error.
>
>>> First, I ran it, and it was an error.
>> Can I ask what Forth this is?
>
>gforth 6.2
That would be a bug. However, I cannot reproduce it.
|
| Show full article (0.82Kb) |
| no comments |
|
  |
|
|
  |
Author: Anton ErtlAnton Ertl Date: Mar 13, 2008 04:10
>0 SET-ORDER
>which indeed breaks gforth.
Yes, that's a bug in 0.6.2. It is fixed in the development version.
- anton
|
| |
| no comments |
|
|
|
|