-
Notifications
You must be signed in to change notification settings - Fork 9
/
Copy pathrequire.fs
140 lines (118 loc) · 4.91 KB
/
require.fs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
\ require.fs
\ Copyright (C) 1995,1996,1997,1998,2000,2003,2006,2007 Free Software Foundation, Inc.
\ This file is part of Gforth.
\ Gforth is free software; you can redistribute it and/or
\ modify it under the terms of the GNU General Public License
\ as published by the Free Software Foundation, either version 3
\ of the License, or (at your option) any later version.
\ This program is distributed in the hope that it will be useful,
\ but WITHOUT ANY WARRANTY; without even the implied warranty of
\ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
\ GNU General Public License for more details.
\ You should have received a copy of the GNU General Public License
\ along with this program. If not, see http://www.gnu.org/licenses/.
\ Now: Kernel Module, Reloadable
create included-files 0 , 0 , ( pointer to and count of included files )
\ note: these names must not contain a "/" or "\"; otherwise a part of
\ that name might be used when expanding "./" (see expandtopic).
here ," *somewhere*" dup c@ swap 1 + swap
, A, here 2 cells -
create image-included-files 1 , A, ( pointer to and count of included files )
\ included-files points to ALLOCATEd space, while image-included-files
\ points to ALLOTed objects, so it survives a save-system
: sourcefilename ( -- c-addr u ) \ gforth
\G The name of the source file which is currently the input
\G source. The result is valid only while the file is being
\G loaded. If the current input source is no (stream) file, the
\G result is undefined. In Gforth, the result is valid during the
\G whole seesion (but not across @code{savesystem} etc.).
loadfilename 2@ ;
: sourceline# ( -- u ) \ gforth sourceline-number
\G The line number of the line that is currently being interpreted
\G from a (stream) file. The first line has the number 1. If the
\G current input source is not a (stream) file, the result is
\G undefined.
loadline @ ;
: init-included-files ( -- ) \ gforth-internal
image-included-files 2@ 2* cells save-mem drop ( addr )
image-included-files 2@ nip included-files 2! ;
: included? ( c-addr u -- f ) \ gforth
\G True only if the file @var{c-addr u} is in the list of earlier
\G included files. If the file has been loaded, it may have been
\G specified as, say, @file{foo.fs} and found somewhere on the
\G Forth search path. To return @code{true} from @code{included?},
\G you must specify the exact path to the file, even if that is
\G @file{./foo.fs}
included-files 2@ 0
?do ( c-addr u addr )
dup >r 2@ 2over str=
if
2drop rdrop unloop
true EXIT
then
r> cell+ cell+
loop
2drop drop false ;
: add-included-file ( c-addr u -- ) \ gforth
\G add name c-addr u to included-files
included-files 2@ 2* cells 2 cells extend-mem
2/ cell / included-files 2!
2! ;
: included1 ( i*x file-id c-addr u -- j*x ) \ gforth
\G Include the file file-id with the name given by @var{c-addr u}.
save-mem 2dup add-included-file
includefilename 2@ 2>r 2dup includefilename 2!
['] read-loop execute-parsing-named-file
2r> includefilename 2! ;
: included ( i*x c-addr u -- j*x ) \ file
\G @code{include-file} the file whose name is given by the string
\G @var{c-addr u}.
open-fpath-file throw included1 ;
: required ( i*x addr u -- i*x ) \ gforth
\G @code{include-file} the file with the name given by @var{addr
\G u}, if it is not @code{included} (or @code{required})
\G already. Currently this works by comparing the name of the file
\G (with path) against the names of earlier included files.
\ however, it may be better to fstat the file,
\ and compare the device and inode. The advantages would be: no
\ problems with several paths to the same file (e.g., due to
\ links) and we would catch files included with include-file and
\ write a require-file.
open-fpath-file throw 2dup included?
if
2drop close-file throw
else
included1
then ;
\ INCLUDE 9may93jaw
: include ( ... "file" -- ... ) \ gforth
\G @code{include-file} the file @var{file}.
name included ;
: require ( ... "file" -- ... ) \ gforth
\G @code{include-file} @var{file} only if it is not included already.
name required ;
\ : \I
\ here
\ 0 word count
\ string,
\ needsrcs^ @ ! ;
\ : .included ( -- ) \ gforth
\ \G list the names of the files that have been @code{included}
\ cr
\ needs^ @
\ BEGIN dup
\ WHILE dup cell+ count type cr
\ 5 spaces
\ dup cell+ count + aligned
\ @ dup IF count type ELSE drop THEN cr
\ @
\ REPEAT
\ drop ;
: .strings ( addr u -- ) \ gforth
\G list the strings from an array of string descriptors at addr
\G with u entries, one per line.
2* cells bounds ?DO
cr I 2@ type 2 cells +LOOP ;
: .included ( -- ) \ gforth
\G list the names of the files that have been @code{included}
included-files 2@ 2 cells under+ 1- .strings ;