...co.uk> writes Re: Parsing text files with standard words [..] 2. define ... be included in the first file. [..] I've seen discussions on ... fundamental problem is that all words, such as INCLUDED, that change ... overcoming this. So whenever a file is INCLUDED the application loses ...-made solutions for this? | execute-parsing ... addr u xt ... unknown execute-...

...ge...@jackson9000.fsnet.co.uk> wrote: FILE-SOURCE ( fileid -- ) is like INCLUDE-FILE but does not invoke the Forth text interpreter i...file position existing at the time FILE-SOURCE is called. CLOSE-SOURCE (...simple example of usage showing how standard words such as REFILL and SOURCE... fileid) begin refill while 0 parse type cr repeat ( fileid) close...

...ge...@jackson9000.fsnet.co.uk> wrote: FILE-SOURCE ( fileid -- ) is like INCLUDE-FILE but does not invoke the Forth text interpreter i... position existing at the time FILE-SOURCE is called. CLOSE-SOURCE ... example of usage showing how standard words such as REFILL and ... fileid) begin refill while 0 parse type cr repeat ( fileid) close ...

...caller of EXECUTE-PARSING-FILE loses control until the word executed (xyz-helper...your example) has completed, whereupon the file is closed. So the caller cannot...with doing that processing in the word that you execute through EXECUTE-...would therefore behave much like INCLUDE-FILE. Are there any conceptual problems .../forth/faq/toc.html New standard: http://www.forth200x.org/forth200x....

... I would prefer to do it via a FILE- SOURCE proposal with EXECUTE-PARSING-FILE as a fall-back. Good! As a...file input stream with a file text input buffer and parse area and a file input stream stack. So, there are words like: LFSOURCE LFPARSE-AREA@ LFPARSE-AREA! ...The user explicity opens and closes the file input stream, and any of the usual parsing words, such ...

..., but that's no big deal. ... FILE-SOURCE and CLOSE-SOURCE can't be ... thing, which is rather different. :) : execute-parsing-file ( fileid xt -- ) r swap file>input execute input ; Without knowing how ... of nesting are used in the word which is processing the input, there'... is required by the ANS Forth standard. I haven't really used exceptions, ...

...>>>design where an application opens a file source and then returns to whatever ...caller of EXECUTE-PARSING-FILE loses control until the word executed (xyz-helper in your example) has completed, whereupon the file is closed. So the caller cannot...caller delegates the processing of the file to xyz-helper via execute-parsing.... This is not so with FILE-SOURCE. So it's not the...

...entrant even if you were using FILE-SOURCE/CLOSE-SOURCE? Not necessarily, ...( fileid xt -- ) r swap file>input execute input ; : read-loop...: included ( fileid -- ) ['] read-loop execute-parsing-file ; Without knowing how many levels...of nesting are used in the word which is processing the input,... required by the ANS Forth standard. But you are right, such ...

...design where an application opens a file source and then returns to whatever..., which would then call EXECUTE-PARSING-FILE. Well yes, but the ... of EXECUTE-PARSING-FILE loses control until the word executed (xyz-...your example) has completed, whereupon the file is closed. So the caller ... delegates the processing of the file to xyz-helper via execute-parsing-file. So it's not ...

...caller of EXECUTE-PARSING-FILE loses control until the word executed (xyz-helper.... After all, part of maintaining standards is removal of things that have...would therefore behave much like INCLUDE-FILE. Are there any conceptual problems ... falls back to the enclosing text interpreter without either CLOSE-SOURCE ...I never considered copying the whole file, yes that works. [...] As this ...