Sujet : Re: single-xt approach in the standard
De : stephen (at) *nospam* vfxforth.com (Stephen Pelc)
Groupes : comp.lang.forthDate : 21. Sep 2024, 15:47:22
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vcmm9q$1kpbh$1@dont-email.me>
References : 1 2 3
User-Agent : Usenapp for MacOS
On 17 Sep 2024 at 15:04:16 CEST, "Ruvim" <
ruvim.pinka@gmail.com> wrote:
There is a point of view (which I don't share) that it is impossible to
implement the standard word `s"` (from the File word set) in a standard
*program*. I.e., that the following definition for `s"` is not standard
compliant:
: s" ( "ccc" -- sd | )
[char] " parse
state @ if postpone sliteral exit then
dup >r allocate throw tuck r@ move r>
; immediate
This effectively means that the classic single-xt approach is impossible
for a standard system.
The problem with definitions such as yours above is that they attempt to
solve the problem of words with "non-default compilation semantics"
(NDCS) using both immediacy and state-smart techniques.
There is nothing in the standard that says it has to be done that way.
The trouble is that the standard provides no tools to implement such
words. We (MPE) provide such tools in VFX Forth 64, which comes
with full source code.
If the standard removes the entitlement to have words such as S" a
significant portion of implementors will just ignore the standard, so reducing
its usefulness.
I suspect that some members of the TC only talk to each other, and have
little or no contact with people who disagree with them on fundamental
issues.
Stephen
-- Stephen Pelc, stephen@vfxforth.comMicroProcessor Engineering, Ltd. - More Real, Less Time133 Hill Lane, Southampton SO15 5AF, Englandtel: +44 (0)78 0390 3612, +34 649 662 974http://www.mpeforth.com MPE website
http://www.vfxforth.com/downloads/VfxCommunity/ downloads