Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #132487
| From | Ruvim <ruvim.pinka@gmail.com> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: Using include-file |
| Date | 2024-10-23 22:43 +0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <vfbg53$25emh$1@dont-email.me> (permalink) |
| References | <vb565d$2vcqf$1@dont-email.me> <2024Sep3.085018@mips.complang.tuwien.ac.at> <vb7mom$3c3ea$1@dont-email.me> |
On 2024-09-03 23:07, Ruvim wrote: > On 2024-09-03 10:50, Anton Ertl wrote: >> Ruvim <ruvim.pinka@gmail.com> writes: >>> Do you know practical cases of using "include-file" in programs? >> >> One way I am thinking about is to implement INCLUDED etc. Systems >> deal differently with relative filenames for INCLUDED, with less >> differences for OPEN-FILE. So if I want to implement a certain >> handling of relative filenames for INCLUDED in order to get rid of >> system differences, one way to do it is to do it for OPEN-FILE and >> then perform INCLUDE-FILE. > > Yes, overriding the system's file search mechanism used by "included" is > a very interesting idea! Another possible reason to not use `INCLUDED`: | INCLUDED may allocate memory in data space before | it starts interpreting the file. So if this effect is unacceptable (for example, if you include part of a definition), then the solution is `INCLUDE-FILE`. Also, `REQUIRED` does not load a file that was loaded by `INCLUDED`. `INCLUDE-FILE` is free of that too. -- Ruvim
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar
Using include-file Ruvim <ruvim.pinka@gmail.com> - 2024-09-03 00:11 +0400
Re: Using include-file mhx@iae.nl (mhx) - 2024-09-02 21:22 +0000
Re: Using include-file mhx@iae.nl (mhx) - 2024-09-03 05:38 +0000
Re: Using include-file rt4all@hetnet.nl (rt) - 2024-11-09 08:29 +0000
Re: Using include-file mhx@iae.nl (mhx) - 2024-11-09 12:06 +0000
Re: Using include-file Stephen Pelc <stephen@vfxforth.com> - 2024-11-09 18:13 +0000
Re: Using include-file dxf <dxforth@gmail.com> - 2024-11-10 13:54 +1100
Re: Using include-file rt4all@hetnet.nl (rt) - 2024-11-10 13:47 +0000
Re: Using include-file anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2024-09-03 06:50 +0000
Re: Using include-file albert@spenarnc.xs4all.nl - 2024-09-03 10:23 +0200
Re: Using include-file mhx@iae.nl (mhx) - 2024-09-03 11:54 +0000
Re: Using include-file sjack@dontemail.me (sjack) - 2024-09-03 15:28 +0000
Re: Using include-file dxf <dxforth@gmail.com> - 2024-09-04 11:36 +1000
Re: Using include-file dxf <dxforth@gmail.com> - 2024-09-04 16:44 +1000
Re: Using include-file Ruvim <ruvim.pinka@gmail.com> - 2024-09-03 23:07 +0400
Re: Using include-file Ruvim <ruvim.pinka@gmail.com> - 2024-10-23 22:43 +0400
Re: Using include-file anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2024-10-24 06:32 +0000
Re: Using include-file albert@spenarnc.xs4all.nl - 2024-10-24 11:30 +0200
Re: Using include-file Ruvim <ruvim.pinka@gmail.com> - 2024-10-26 09:19 +0400
Re: Using include-file Gerry Jackson <do-not-use@swldwa.uk> - 2024-09-04 10:54 +0100
Re: Using include-file Gerry Jackson <do-not-use@swldwa.uk> - 2024-09-04 11:09 +0100
Re: Using include-file dxf <dxforth@gmail.com> - 2024-09-04 21:13 +1000
Re: Using include-file Ruvim <ruvim.pinka@gmail.com> - 2024-09-17 18:33 +0400
Re: Using include-file minforth@gmx.net (minforth) - 2024-10-24 12:44 +0000
Re: Using include-file Ruvim <ruvim.pinka@gmail.com> - 2024-10-27 21:31 +0400
Re: Using include-file minforth@gmx.net (minforth) - 2024-10-27 22:32 +0000
csiph-web