Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #49761
| Newsgroups | comp.lang.forth |
|---|---|
| Date | 2016-08-03 01:18 -0700 |
| References | <0a8d7b8a-8367-4e92-a482-ee8b6728325a@googlegroups.com> |
| Message-ID | <c5aa8e30-1dee-4d64-9022-e24f46b20437@googlegroups.com> (permalink) |
| Subject | Re: Code management with wordlists |
| From | hheinrich.hohl@gmail.com |
On Tuesday, August 2, 2016 at 1:00:40 PM UTC+2, Julian Fondren wrote: > 1. Bare bones ANS > 2. VOCABULARY > 3. Beheading > 4. Packages We should add the following two methods to the list: ----------------------------------------------------------------------- 5. Modules Modules are implemented in VFX Forth and used as follows: MODULE <name> : word1 ... ; : word2 ... ; : word3 ... ; EXPORT word3 END-MODULE All words defined inside the module are hidden except for the ones that are exported before the end of the module. Ulrich Hoffmann describes this method in detail. See http://theforth.net/package/modules Article in German language: Forth Magazin "Vierte Dimension" VD 2016-02, Seite 15 Download currently: http://85.214.243.249/filemgmt_data/files/4d2016-02.pdf Modules are rather similar to packages. In packages, you decide between private and public on a word-by-word basis. In modules, every word is private from the beginning. At the end, you export some words to make them public. Both methods have their advantages. ----------------------------------------------------------------------- 6. Excising This method was used in LMI PC/FORTH and UR/FORTH. EXCISE <word1> <word5> This command hides the headers of <word1> through <word5> by excising their headers from the linked list in the dictionary. Together with the ability to create binary overlays, the LMI FORTH compilers enabled the user to create modules that showed only words that are relevant for the end user.
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Code management with wordlists Julian Fondren <julian.fondren@gmail.com> - 2016-08-02 04:00 -0700
Re: Code management with wordlists peter.m.falth@gmail.com - 2016-08-02 05:03 -0700
Re: Code management with wordlists hughaguilar96@gmail.com - 2016-08-02 14:40 -0700
Re: Code management with wordlists Mark Wills <markwills1970@gmail.com> - 2016-08-02 07:15 -0700
Re: Code management with wordlists Mark Wills <markwills1970@gmail.com> - 2016-08-02 07:16 -0700
Re: Code management with wordlists Paul Rubin <no.email@nospam.invalid> - 2016-08-02 10:40 -0700
Re: Code management with wordlists hheinrich.hohl@gmail.com - 2016-08-03 01:18 -0700
Re: Code management with wordlists JennyB <jennybrien@googlemail.com> - 2016-08-03 03:17 -0700
Re: Code management with wordlists hughaguilar96@gmail.com - 2016-08-03 10:47 -0700
Re: Code management with wordlists Julian Fondren <julian.fondren@gmail.com> - 2016-08-03 10:59 -0700
Re: Code management with wordlists peter.m.falth@gmail.com - 2016-08-04 00:45 -0700
Re: Code management with wordlists "HAA" <someone@microsoft.com> - 2016-08-04 23:14 +1000
Re: Code management with wordlists peter.m.falth@gmail.com - 2016-08-04 06:44 -0700
Re: Code management with wordlists "HAA" <someone@microsoft.com> - 2016-08-05 10:26 +1000
Re: Code management with wordlists JennyB <jennybrien@googlemail.com> - 2016-08-04 02:35 -0700
Re: Code management with wordlists JennyB <jennybrien@googlemail.com> - 2016-08-05 02:54 -0700
Re: Code management with wordlists krishna.myneni@ccreweb.org - 2016-08-06 08:25 -0700
csiph-web