Google

SEARCH-ORDER-EXT Search-order + extensions

The Search Order Word Set as defined by the Standard.

Note that there a some extensions in the Portable Forth Environment. Wordlists can be made case-sensitive always or only at request. Wordlists can be linear or hashed vocabularies. There are other words to recursivly search an implicit vocabulary along with another.



DEFINITIONS ( -- )  
ansi 16.6.1.1180
make the current context-vocabulary the definition-vocabulary, that is where new names are declared in. see ORDER

reference: p4_definitions in ../src/search.c:0039, export CO DEFINITIONS

FORTH ( -- voc )  
ansi 16.6.1.1595
return the voc-address of the base FORTH-vocabulary

reference: p4_forth_wordlist in ../src/search.c:0216, export CO FORTH-WORDLIST

GET-CURRENT ( -- voc )  
ansi 16.6.1.1643
return the current definition vocabulary, see DEFINITIONS

reference: p4_get_current in ../src/search.c:0047, export CO GET-CURRENT

GET-ORDER ( -- vocn ... voc1 n )  
ansi 16.6.1.1647
get the current search order onto the stack, see SET-ORDER

reference: p4_get_order in ../src/search.c:0055, export CO GET-ORDER

SEARCH-WORDLIST ( str-ptr str-len voc -- 0 | xt 1 | xt -1 )  
ansi 16.6.1.2192
almost like FIND or (FIND) -- but searches only the specified vocabulary.

reference: p4_search_wordlist in ../src/search.c:0070, export CO SEARCH-WORDLIST

SET-CURRENT ( voc -- )  
ansi 16.6.1.2195
set the definition-vocabulary. see DEFINITIONS

reference: p4_set_current in ../src/search.c:0089, export CO SET-CURRENT

SET-ORDER ( vocn ... voc1 n -- )  
ansi 16.6.1.2197
set the search-order -- probably saved beforehand using GET-ORDER

reference: p4_set_order in ../src/search.c:0098, export CO SET-ORDER

WORDLIST ( -- voc )  
ansi 16.6.1.2460
return a new vocabulary-body for private definitions.

reference: p4_wordlist in ../src/search.c:0115, export CO WORDLIST

ALSO ( -- )  
ansi 16.6.2.0715
a DUP on the search ORDER - each named vocabulary replaces the topmost ORDER vocabulary. Using ALSO will make it fixed to the search-order. (but it is not nailed in trap-conditions as if using DEFAULT-ORDER )
 order:   vocn ... voc2 voc1 -- vocn ... voc2 voc1 voc1

reference: p4_also in ../src/search.c:0129, export CO ALSO

ORDER
ansi 16.6.2.1985

no forth documentation available   (p4_order)

  • see the ANSI Documentation of this word : ansi 16.6.2.1985

reference: p4_order in ../src/search.c:0158, export CO ORDER

PREVIOUS ( -- )  
ansi 16.6.2.2037
the invers of ALSO , does a DROP on the search ORDER of vocabularies.
 order: vocn ... voc2 voc1 -- vocn ... voc2 
 example: ALSO PRIVATE-VOC DEFINTIONS (...do some...) PREVIOUS DEFINITIONS

reference: p4_previous in ../src/search.c:0180, export CO PREVIOUS

DEFAULT-ORDER ( -- )  

nail the current search ORDER so that it will even survive a trap-condition. This default-order can be explicitly loaded with RESET-ORDER

reference: p4_default_order in ../src/search.c:0198, export CO DEFAULT-ORDER

RESET-ORDER ( -- )  

load the DEFAULT-ORDER into the current search ORDER - this is implicitly done when a trap is encountered.

reference: p4_reset_order in ../src/search.c:0208, export CO RESET-ORDER