[383] 2025-07-19 01:57:17 EricBlake wrote:

requestClarification - What should the behavior be if the system has no hard-coded limit on size?

On a system where the data space grows dynamically, there is no inherent compile-time limit on the maximum address in data space, and there might be no easy way to probe at runtime how large of an address can be allocated without failure. In that scenario, is it better to include the word UNUSED and have it return -1 to indicate unknown (or rather, the maximum unsigned integer since the prototype uses 'u'), or to omit the word UNUSED from the core extension set? Some traditional systems had MORECORE for adding more storage to the data space when UNUSED indicated that the current space was insufficient, but MORECORE is not standardized.

[r1452] 2025-07-11 13:18:22 achowe replies:

requestClarification - Wording on ccc prohibits \" inside S\"

Forth 200x Draft 19.1 section 6.2.2266 S\" Translation Rules allow \" as an escape sequence to embed a literal " in a string. I expect the description here extends the definition of ccc to account for escaped characters.

[r1453] 2025-07-11 13:19:49 achowe replies:

requestClarification - Wording on ccc prohibits \" inside S\"

Quick test case

t{ S\" 123 S\" 432\" TYPE " EVALUATE -> 123 }t