Confusion over S" and SLITERAL

[SirWumpus]

The Forth 200x Draft 19.1 for S" defines both interpretation and compilation semantics, while 17.6.1.2212 SLITERAL is compile-only. The Rationale A.17.6.1.2212 SLITERAL suggests that it can be used to define 6.1.2165 S" .

: S" ( "ccc<quote>" -- )
     [CHAR] " PARSE POSTPONE SLITERAL
; IMMEDIATE 

Does this not imply that SLITERAL must also perform the S" interpretation semantics too?

This appears to be an oversight between the Forth 2012 standard and the proposed Draft. In the standard S" (and S\") and SLITERAL have compile-only semantics and so work together nicely, while in the Draft S" (and S\") now have interpretation semantics, but failed to update SLITERAL and its Rationale to address the change.

Is this a failure (bug) in the proposed Draft or am I missing something with respect to SLITERAL implementation?

[ruv]

Does this not imply that SLITERAL must also perform the S" interpretation semantics too?

This example implementation was correct in Forth-2012, and it just become incorrect in the new draft.

There are two versions for the word s" in Forth-2012 — CORE (6.1.2165) and FILE (11.6.1.2165). And a difference is that interpretation semantics are undefined in the CORE version.

The rationale A.17.6.1.2212 provides an example for the CORE version, it says: "The current functionality of 6.1.2165 S" may be provided by the following definition". So, it provides an example for the CORE version of s", that cannot be used in interpretation state by a standard program.

On the standard meeting in 2017 it was decided to remove the FILE version of s", and update the CORE version of s" (move from FILE).

This appears to be an oversight between the Forth 2012 standard and the proposed Draft.

Yes, you are right — it's an oversight.

am I missing something with respect to SLITERAL implementation?

No. sliteral was not changed.