…about everything that is not specific to the standard or the systems, but this website itself
GeraldWodni  Digests and Meta discussionExample2016-01-08 18:42:54
First let me thank you all for putting life in this website by contributing ;) If you have feedback and ideas, please let me know and discuss it here: Meta Discussion
As Peter Knaggs suggested a while ago, the system now features digests. That should make it far easier to keep discussions alive without polling the website. If you do not wish to receive any digests, please disable them in your profile (you will find a link at the very bottom).
Moderators can now lift users from "moderated" to "unmoderated" in the Manage User Section, that will allow them to post without delay. Pending contributions are also shown to the moderators in their digests.
AntonErtl  Session timer and preseving contributionsExample2016-12-31 22:07:36
I just wrote a long reply, taking my time. At the end my session had timed out, the system asked for authentication and presented an empty text field instead of the result of my long editing session. Please fix:
longer session time.
Upon session timeout, preserve the state of the session across the authentication screen.
juergenuk  Standard 2012 as slightly reduced version - but as Part of the Forth BookshelfSuggested reference implementation2018-02-25 11:57:31
when I fell over the standard here, I wondered why it is not more known, promoted and probably used.
As result I downloaded the PDF and tried to squeeze it into an additional eBook to make it part of the Forth Bookshelf. To give it some value as eBook, I would list it with the same costing the usual $4 to cover the done and additional work, in the future. As people can see the relevant links in the preview, they will know where to find the free PDF and can decide if it is worth buying the eBook. But the promotion to the Standard has been achieved anyway. I contributed it to Stephen Pelc who gave me so much support with my journey with Forth over the last 5 years. As well MPE made the VFXTESTAPP available, MSP430LITE and ARM LIT in addition to the commercial products.
This year is 50 Years Of Forth.
When I started writing / collecting for A Start With Forth Part 2
- I saw that referencing to this documentation would be quite helpful for the ones who want to Start With Forth.
The probelm I see now that it is not clear who would be the company / body / person within the Forth Community to give the ok for such a venture,
as done with all the other eBooks asking Chuck, Leon, Stephen, Ting, Leo and others
to make sure we have such a Forth Bookshelf. without copyright violations, which is acually visible worldwide on amazon and amazon actually sometimes runs advertising emails about Forth - encluding my eBooks.
The A Taste of the 2012 Forth Standard is nearly ready and I sent a partial PDF to Stephen for guidance, and he suggested to ask here.
Looking forward to your feedback.
This eBook that can be read on tablets and Mobiles as well, is shortened to the parts that can be read easily on Mobiles. The Contents pages further down show the original list and an i shows which parts are included ( or too difficult to reformat - so I left them out ). it relates to the Complete Document and shows which parts are included
- but the link to the complete Document is included anyway.
Contents Page of the full Standards document is shown and the link to it ( and pages _i marked sections are included in this eBook ) The full document for free download can be found at http://forth-standard.org/ and at http://www.forth200x.org/
Page numbers relate to the original PDF document so people can go there easily
Contents v_i Foreword vi_i Proposals Process vii_i 200x Membership x_i
1 Introduction 13_i 1.1 Purpose 13_i 1.2 Scope 13_i 1.2.1 Inclusions 13_i 1.2.2 Exclusions 13_i 1.3 Document organization 13_i 1.3.1 Word sets 13_i 1.3.2 Annexes 14_i 1.4 Future directions 14_i 1.4.1 New technology 14_i 1.4.2 Obsolescent features 14_i
2 Terms, notation, and references 16_i 2.1 Definitions of terms 16_i 2.2 Notation 19_i 2.2.1 Numeric notation 19_i 2.2.2 Stack notation 19_i 2.2.3 Parsed-text notation 19_i 2.2.4 Glossary notation 19_i 2.2.5 BNF notation 20_i 2.3 References 21_i
3 Usage requirements 22_i 3.1 Data types 22_i 3.1.1 Data-type relationships 22_i 3.1.2 Character types 23_i 3.1.3 Single-cell types 24_i 3.1.4 Cell-pair types 26_i 3.1.5 System types 26_i 3.2 The implementation environment 27_i 3.2.1 Numbers 27_i 3.2.2 Arithmetic 27_i 3.2.3 Stacks 28_i 3.2.4 Operator terminal 29_i 3.2.5 Mass storage 29_i 3.2.6 Environmental queries 29_i 3.2.7 Obsolescent Environmental Queries 29_i
3.3 The Forth dictionary 30_i 3.3.1 Name space 30_i 3.3.2 Code space 31_i 3.3.3 Data space 31_i
3.4 The Forth text interpreter 33_i 3.4.1 Parsing 34_i 3.4.2 Finding definition names 35_i 3.4.3 Semantics 36_i 3.4.4 Possible actions on an ambiguous condition 36_i 3.4.5 Compilation 37_i
4 Documentation requirements 38 4.1 System documentation 38 4.1.1 Implementation-defined options 38 4.1.2 Ambiguous conditions 39 4.1.3 Other system documentation 41 4.2 Program documentation 41 4.2.1 Environmental dependencies 41 4.2.2 Other program documentation 42
5 Compliance and labeling 43 5.1 Forth-2012 systems 43 5.1.1 System compliance 43 5.1.2 System labeling 43 5.2 Forth-2012 programs 43 5.2.1 Program compliance 43 5.2.2 Program labeling 43
6 Glossary 44 6.1 Core words 44 6.2 Core extension words 73
7 The optional Block word set 86 8 The optional Double-Number word set 92 9 The optional Exception word set 98 10 The optional Facility word set 103 11 The optional File-Access word set 114 12 The optional Floating-Point word set 126 13 The optional Locals word set 146 14 The optional Memory-Allocation word set 152 15 The optional Programming-Tools word set 155 16 The optional Search-Order word set 165 17 The optional String word set 170 18 The optional Extended-Character word set 175
A Rationale 182 A.1 Introduction 182 A.2 Terms and notation 182 A.3 Usage requirements 183 A.4 Documentation requirements 197 A.5 Compliance and labeling 197 A.6 Glossary 198 A.7 The optional Block word set 214 A.8 The optional Double-Number word set 214 A.9 The optional Exception word set 216 A.10 The optional Facility word set 217 A.11 The optional File-Access word set 221 A.12 The optional Floating-Point word set 223 A.13 The optional Locals word set 226 A.14 The optional Memory-Allocation word set 227 A.15 The optional Programming-Tools word set 227 A.16 The optional Search-Order word set 230 A.17 The optional String word set 231 A.18 The optional Extended-Character word set 232
B Bibliography 234_i
C Compatibility analysis 236_i C.1 FIG Forth (circa 1978) 236_i C.2 Forth 79 236_i C.3 Forth 83 236_i C.4 ANS Forth (1994) 237_i C.5 ISO Forth (1997) 237_i C.6 Approach of this standard 238_i C.7 Differences from Forth 94 238_i C.8 Additional words 241_i
D Portability guide 244_i D.1 Introduction 244_i D.2 Hardware peculiarities 244_i D.3 Number representation 246_i D.4 Forth system implementation 247_i D.5 Summary 248_i
E Alphabetic list of words 249_i
I understand that people might believe that such an eBook might not be necessary
- but if giving the copyright JUST for the publication is acceptable, I assume the people who are being made aware of the Standard will appreciate it as they do the other eBooks of the Bookshelf
- and can always look into it, see the link to the location here and decide then if they want to buy it to look at it on the move easily.
Looking forward to your feedback.
Kind regards Juergen
StephenPelc  Need lock on already posted commentsExample2018-05-24 12:28:32
When you post a reply, you easily get back to the reply with the submit button. If you press submit again, another copy of the reply is posted ... and again ... and again? A user should not be able to post the same reply twice while logged in.
GerryJackson  How to change email addressRequest for clarification2018-06-06 12:08:03
My email address was withdrawn from use by EE about a year ago and I no longer receive the digest. I can find no way on this website to change my email address. Can you do it for me?
Or must I re-register under a different user name and let the old one fester?
Better still add a way of doing it in 'Settings' next to change password
alextangent  Searching for ] (right-bracket) doesn't return ]Proposal2019-08-01 16:07:34
mcondron  Search boxComment2019-08-10 00:39:41
It would be very nice if somehow the code for the website could be modified so that when you click on "Search" at the top bar, the cursor automatically goes to the Search text box. As it is now, you have to click the mouse on that box before you can start typing into it.
GeraldWodni  Overhaul 2020: ProposalsComment2020-06-23 22:45:08
All proposals have been moved from their (often randomly choosen urls) to
Each proposal has a state, which is explained in this flowchart (position subject to change).
To help new proponents structuring their proposal, a template and a link to the guidlines has been added.
ruv  Support several versions of the standard in parallelComment2022-09-07 11:41:37
At the moment, forth-standard.org contains only Forth-2012. When the next standard will be published, it should be on forth-standard too, in parallel with Forth-2012, I think. What do you think?
If we want to provide several versions in parallel, the URI space should be developed accordingly. Since currently the URI space supports only one version. For example, in the URI https://forth-standard.org/standard/words the fragment standard refers Forth-2012.
A website example that supports several versions of a document in parallel: https://www.postgresql.org/docs/
GeraldWodni  Overhaul 2022Comment2023-02-19 11:03:02
Bracket-id prefixed for all contribution subjects for easier communication
[\<id\>] \<subject\> (was just used for proposals before).
Search supports finding contributions, just put brackets around the desired id. Search for
 will jump you to the overhaul-contribution of 2020.
To further simplify referring to contributions, one can use the
/jump-to/\<id\> link (this is also used by the search). https://forth-standard.org/jump-to/140 will also take you search result from above.
JackPope  implementation standardsSuggested reference implementation2023-07-06 16:56:37
I am thinking about (maybe proposing) language implementation standards for Forth language classifications, such as:
- FDI: Forth Dictionary Implementation; a minimum percentage of Forth words implemented by the language.
- FPI: Forth Paradigm Implementation; some minimal Forth type bootstrapping from a host language or chip instruction set.
- FOL: Forth Like; resembles Forth, but not FDI and not FPI.
- FLI: Forth Language Implementation; is both FDI and FPI.
Such taxonomy could assist programming language developers in their planning/goals, while giving new users of a "Forth" an immediate indication of its limits and potential.
My apologies if I missed prior communiques related to this subject, or if another Forth forum is better suited to this discussion.
AntonErtl  Proposals and the documentComment2023-12-01 18:08:40
At some point (hopefully soon) the editor (i.e., I) will integrate the accepted proposals into the standard document. In order to see which proposals have yet to be integrated, I would like to have one of the following:
A proposal state "accepted and integrated", that is reached from "accepted" once it is integrated into the document. I would prefer this.
Sorting of the accepted proposals by acceptance date/acceptance reply, not by proposal number. In that case I could track what is the most recently accepted proposal that has been integrated, and not consider any proposal below. As it is, an accepted proposal can appear anywhere in the list of accepted proposals, and I would have to scan that repeatedly (with the danger of missing one). This order may also be useful for other users of forth-standard.org, because they also want to keep up-to-date on the accepted proposals without repeatedly scanning the list.
AntonErtl  CfVs after committee decisionComment2023-12-02 10:43:31
Most additions to the standard are optional, and even if an addition is implemented in a system after a proposal is accepted, that does not happen immediately. The system implementor may decide to wait until the next release of the standard happens, and even after that it may take some years. Similarly, programmers do not start using a newly standardized feature immediately, but only once the systems the programmer is interested in provide it.
In order to have an overview of the status of an proposal in the community, it is useful to be able to report updates about system support or usage (i.e., to "vote") for the proposal even after the committee has accepted it and even after it has been integrated into the standard document.
In case of a rejection by the committee such updates can be useful, too. They may inform potential alternative proposals. However, given that the CfV result is for a specific proposal version, I think that, once a proposal has reached CfV stage, it should not revert to informal or formal; instead, the voted-on proposal should be retired, and a new proposal with the needed changes should be started.