-
Notifications
You must be signed in to change notification settings - Fork 1
/
rfds.html
347 lines (260 loc) · 14.4 KB
/
rfds.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
<html><head>
<title>Forth extension proposal RfDs and CfVs</title>
</head><body>
<h1>Forth extension proposal RfDs and CfVs</h1>
[ <a href="forth200x.html">About Forth 200<em>x</em></a>
| <a href="documents/">Forth 200x draft documents</a>
| <a href="proposals.html">Other proposals</a>
| <a href="rfd-guide.html">How to write an RfD</a> ]
<h2>About Forth200<em>x</em></h2>
There is a new Forth standardization effort underway. This page is
about the proposals for extensions/changes, you can read more about
other aspects of the standards effort on the <a
href="forth200x.html">Forth 200<em>x</em></a> page.
<h2>Forth-2012</h2>
The <a href="http://www.forth200x.org/documents/forth-2012.pdf">Forth-2012
document</a> is now available. You can also look at it in HTML form
at <a href="http://forth-standard.org/standard/words">forth-standard.org</a><!--
and
a <a href="http://www.forth200x.org/documents/html/contents.html">simple
HTML version</a>-->. Gerry Jackson has written/collected
a <a href="https://github.com/gerryjackson/forth2012-test-suite">test
suite</a> for testing the compliance of systems with Forth-2012
(beyond our own tests).
<p>We continue working after reaching this milestone.
<!--<h2>Public Review</h2>
<p>
The third release candidate (RC3) of the proposed Forth 2012 standard
(<a href="documents/forth-rc3.pdf">download</a>)
was released for public review on 28 September 2014.
This is a one month review period, the committee will meet in
November 2014 to review any comments received.
Formal comments on the proposed standard should be posted to the
<a href="http://groups.yahoo.com/group/forth200x/">Forth 200x</a>
mail list.
</p>
-->
<h3>Document Archive</h3>
<p>
There is a <a href="documents/">public archive</a> of previous drafts.
These documents are available as PDF and in some cases the
<a href="http://www.latex-project.org">LaTeX</a> source is also available.
</p>
<h2>Recent RfDs</h2>
See <a href="#rfds-without-cfv">below</a> for older RfDs without CfVs.
<ul>
<li> <a href="http://forth-standard.org/standard/tools/SYNONYM#contribution-60">Tighten the specification of SYNONYM</a>
<li> <a href="http://forth-standard.org/standard/core/FIND#contribution-58">FIND-NAME</a>
<li> <a href="http://forth-standard.org/standard/core/FIND#reply-165">Clarify FIND</a>
<li> <a href="http://forth-standard.org/standard/exception/THROW#contribution-36">EXCEPTION LOCALs</a>
<li> <a href="http://forth-standard.org/standard/core/BL#contribution-34">BL rationale is wrong</a>
</ul>
The above are the proposals
on <a href="forth-standard.org">forth-standard.org</a> since the 2017
meeting (when we decided that new proposals should be put there).
Below you find RfDs that were started before that meeting.
<ul>
<li> <a href="drop-double-input.txt">Drop double numbers as input format (comp.lang.forth only)</a>
<li> <a href="cs-drop.txt">CS-DROP</a> (Email only)
<li> <a href="u-d-less-than.txt">Unsigned Double Words Naming Convention</a> (Mailing list submission missing)
<li> <a href="doublesyntax.txt">New double syntax</a>
<li> <a href="https://forth-standard.org/proposals/recognizer#contribution-142"X>Recognizers</a> (<a href="Recognizer-rfc-D-comments.html">comments</a> (originally part of the proposal, but then split out), <a href="Recognizer-rfc-C.html">v3</a>, <a href="Recognizer-rfc-B.html">v2</a>, <a href="Recognizer-rfc.html">v1</a>)<!--https://web.archive.org/web/20190705062841/http://amforth.sourceforge.net/pr/Recognizer-rfc-D-comments.html (<a href="https://web.archive.org/web/20160328150204/http://amforth.sourceforge.net/pr/Recognizer-rfc-C.html">v3</a>, <a href="https://web.archive.org/web/20160328150204/http://amforth.sourceforge.net/pr/Recognizer-rfc-B.html">v2</a>, <a href="https://web.archive.org/web/20160328150204/http://amforth.sourceforge.net/pr/Recognizer-rfc.html">v1</a>)-->
</ul>
<h2>Current CfV Standings</h2>
No current CfVs.
<ul>
</ul>
<h2>CfV results</h2>
<h3>Accepted at the 2017 Forth200<em>x</em> meeting</h3>
<ul>
<li> <a href="quotations.txt">Quotations</a> (<a href="quotations-v1.txt">v1</a>, <a href="quotations-v2.txt">v2</a>, <a href="quotations-v3.txt">v3</a>)
</ul>
<h3>Accepted at the 2016 Forth200<em>x</em> meeting</h3>
<ul>
<li> <a href="to-f-round">D>F and S>F</a> (RfDs: <a href="to-f-round-v1">v1</a>, <a href="to-f-round-v2">v2</a>)
<li> <a href="char-is-1.html">1 chars = 1</a>
</ul>
<h3>Accepted at the 2015 Forth200<em>x</em> meeting</h3>
<ul>
<li> <a href="twos-complement.html">2s-Complement Wrap-Around Integers</a>
</ul>
<h2>Proposals included in Forth-2012</h2>
<h3>Accepted at the 2014 Forth200<em>x</em> meeting</h3>
<ul>
<li><a href="s-escape-quote.html">Interpreted S\"</a></li>
</ul>
<h3>Accepted at the 2013 Forth200<em>x</em> meeting</h3>
<ul>
<li><a href="traverse-wordlist.html">TRAVERSE-WORDLIST</a>
</ul>
<h3>Accepted at the 2012 Forth200<em>x</em> meeting</h3>
<ul>
<li><a href="s-to-f.html">S>F and F>S</a>
</ul>
<h3>Accepted at the 2011 Forth200<em>x</em> meeting</h3>
<ul>
<li> <a href="locals.html">Enhanced local variable syntax</a>
(<a href="locals-v6.1.txt">v6.1</a>,
<a href="locals-v6.txt">v6</a>,
<a href="locals-v5.txt">v5</a>,
<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/9977213afa4a478e">v2</a>,
<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/8e0bc665e0b0e83b">v1</a>)
</li>
<li> <a href="buffer.html">BUFFER:</a>
(<a href="buffer.txt">2009-02-04</a>)</li>
<li> <a href="text-substitution.txt">Text Substitution</a></li>
</ul>
<h4>Wording Changes</h4>
<ul>
<li> <a href="is.html">IS</a>
<li> Multi-tasking Block Buffers (included in the "ed11" changes in the document)
</ul>
<h3>Accepted at the 2010 Forth200<em>x</em> meeting</h3>
<ul>
<li> <a href="xchar.html">XCHAR wordset</a>
(<a href="xchar.txt">v4</a>,
<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/cb7f1c5993e42628">v2</a>,
<a href="http://groups.google.com/group/comp.lang.forth/msg/5fccc7e3a5b49fac?dmode=source">v1</a>)</li>
<li> <a href="synonym.html">Synonym</a>
(<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/d929c03f4bff10fe">v2</a>,
<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/d9530da1cfce9b04">v1</a>)</li>
<li> <a href="escaped-strings.html">Escaped Strings</a>
(<a href="http://groups.google.co.uk/group/comp.lang.forth/browse_thread/thread/ec726cba4f65a5b1">v5</a>,
<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/9c43be0f22938ca6/">v4</a>,
<a href="http://groups.google.com/group/comp.lang.forth/msg/c0d7da8e92bc33ba">v3</a>,
<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/6128851a85ebe49a">v2</a>,
<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/c18d96f223f15ad1">v1</a>)</li>
<li> <a href="n-to-r.html"><code>N>R</code> and <code>NR></code></a>
(<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/cd191a4e56f8e3e0">v2</a>,
<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/1baf8cf8d8d146ad">v1</a>)</li>
</ul>
<h4>Wording changes</h4>
<ul>
<li> <a href="wordset-queries.html">Wordset queries</a>
<li> <a href="ekey-event.html">Ekey Event Record</a>
(<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/172831b286f03e47/569c63824f9ab9b5">v1</a>) only 1-3 accepted; also delete last paragraph of Rationale</li>
<li> <a href="legacy.html">Legacy Words</a>
(<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/2bac3e45169e4af9">v3</a>,
<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/c791294690c65d74">v2</a>,
<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/7652401a2f794f7c">v1</a>)
only 1-3 accepted; FORGET is still in but still obsolescent
<li> <a href="rfc.html">RfC (Wording changes)</a>
(<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/89a4695a4e8bd3c0/77de59074abc69ec">v1</a>)</li>
<li> <a href="structures2.html">Structures wording</a>
(<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/5d4180b7041fd57">v2</a>,
<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/c327a52bbbec1321">v1</a>)
</ul>
<h3>Accepted at the 2009 Forth200<em>x</em> meeting</h3>
<ul>
<li> <a href="ftrunc.html">Floating point truncation</a>
<li> <a href="fasinh-lt0.html">Unneeded restriction in FASINH</a>
<li> <a href="fatan2.html">Ambiguity in FATAN2</a>
<li> <a href="2value.html">2VALUE</a>
<li> <a href="fvalue.html">FVALUE</a>
</ul>
<h4>Wording changes</h4>
<ul>
<li> <a href="name-length.txt">Definition Name Length</a>
<li> <a href="associate-assign.txt">Assign</a>
<li> <a href="key-ekey.txt">KEY/EKEY</a> (only items 1-5 accepted)
</ul>
<h3>Accepted at the 2008 Forth200<em>x</em> meeting</h3>
<ul>
<li> <a href="fp-stack.html">Separate FP Stack</a>
</ul>
<h3>Accepted at the 2007 Forth200<em>x</em> meeting</h3>
<ul>
<li> <a href="number-prefixes.html">Number Prefixes</a>
<li> <a href="throw-iors.html">THROW IORs</a>
<li> <a href="structures.html">Structures</a>
<li> <a href="ekeys.html">EKEY return values</a>
</ul>
<h3>Accepted at the 2006 Forth200<em>x</em> meeting</h3>
<ul>
<li> <a href="required.html">One-time file loading</a>
</ul>
<h3>Accepted at the 2005 Forth200<em>x</em> meeting</h3>
<ul>
<li><a href="defined.html">[DEFINED] and [UNDEFINED]</a> <!-- original RfD: Message-ID: <[email protected]> -->
<li><a href="parse-name.html">PARSE-NAME</a>
<li><a href="extension-query.html">Extension queries</a>
<li><a href="deferred.html">Deferred words</a>.
</ul>
<h2><a name="rfds-without-cfv">RfDs without CfVs</a></h2>
<ul>
<li> <a href="colon-name.txt">:NAME</a>
<li> <a href="internationalisation.txt">Internationalisation</a>
<li> <a href="ieee-fp.txt">IEEE FP</a>
<li> <a href="fnegate-zero.txt">FNEGATE specification for signed zero</a>
<li><a href="memory-2010-06-26.txt">Memory Access Words</a>
(<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/5bc6daa1f5e38c6b">v2</a>,
<a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/98cbade35bfe5eb0">v1</a>)
<li><a href="http://tech.groups.yahoo.com/group/forth200x/message/448">SIZE</a> (email-only yet)
<li><a href="http://tech.groups.yahoo.com/group/forth200x/message/318">HEADER</a> (email-only yet)
<li><a href="http://tech.groups.yahoo.com/group/forth200x/message/298"><BUILDS</a> (email-only yet)
<li> <a href="found.txt">FOUND</a>
</ul>
<h2>Shelved RfDs</h2>
<ul>
<li> <a href="directories1.html">File Names and Directories</a> (withdrawn due to lack of support)
<li> <a href="directories.html">Directories</a> (withdrawn due to vigorous resistance)
<li> <a href="http://groups.google.com/group/comp.lang.forth/browse_thread/thread/7f8c1c9493783a82">c-addr/len</a> (widthdrawn due to intorduction of <code>pchar</code>).
<li> <a href="unobsolete-forget.txt">Unobsolete FORGET</a> (incorporated into <a href="legacy.html">Legacy Wordset</a>
<li> <a href="http://groups.google.com/group/comp.lang.forth/msg/c0972519979b110d">!ME and @ME</a> (withdrawn <a href="http://groups.google.com/group/comp.lang.forth/msg/42c1f9c6081cbd49"><1695ec44-b35c-4f0d-9065-884ad1df106e@r27g2000yqn.googlegroups.com></a>)
<li> <a href="file-source.html">FILE-SOURCE STRING-SOURCE and CLOSE-SOURCE</a> (withdrawn because of mostly-negative responses)
<li> <a href="paren-star.txt">(* comments *)</a> (withdrawn <a href="http://groups.google.at/group/comp.lang.forth/msg/dbc5b48e6028f915"><[email protected]></a>)</li>
<li> <a href="http://groups.google.com/group/comp.lang.forth/msg/4c74385eafd71198?dmode=source">Object Extensions</a> (withdrawn, no reason given)
<li><a href="parse-word.html">PARSE-WORD</a> (replaced by <a href="parse-name.html">PARSE-NAME</a>).
</ul>
<h2>Code</h2>
Tests or reference implementations are missing from some proposals
(yet).
<ul>
<li>Reference implementations <a href="reference-implementations/">for
all classes of proposals</a>.
<li>Tests <a href="tests/">for all classes of proposals</a>
<li> <a href="forth200x-code.zip">Zip
file</a> for reference implementations and tests for CfVs (frozen proposals).
</ul>
<h2><a name="process">About the RfD/CfV process</a></h2>
There have been some thoughts about revising the standard. In order
to do that, those in the standards committee should know what the
system implementors and the programmers are already doing in that
area, and what they would be willing to do, or wish for.
<p>To do that, I am trying a system here that is somewhat like the
RfD/CfV system for deciding about newsgroups: A proponent of an
extension or change to the standard writes up a proposal; this
proposal is then published here as an RfD (request for discussion),
and others can then comment on the proposal; the proponent can modify
the proposal, taking the comments into consideration, or he can ignore
some of the comments (if that's a problem for the commenters, they can
make a competing proposal, or somesuch).
<p>Anyway, once a proposal has settled down, it enters the CfV (call for
votes) stage, where system implementors state, whether their system
implements this proposal, or what the chances are that it ever will.
Similarly, programmers can state whether they have used stuff like
that proposed, and whether they would use the proposed extension once
it is standardized. After a deadline, a preliminary poll result will
be published, but the poll will remain open for adding to the Web page
(especially system implementors are invited to do that).
<p>Proposals in the CfV stage are eligible for inclusion in the
Forth200<em>x</em> standard, and many have been included already.
<h2>Related Processes</h2>
As mentioned above, this process was inspired by the RfD/CfV system
that helps news admins decide which newsgroups they should provide on
their Usenet news servers; the corresponding roles are:
<ul>
<li> news servers - Forth systems
<li> news admins - Forth system implementors
<li> Usenet posters and lurkers - Forth programmers
</ul>
<p>A similar process, and closer in subject matter, is the <a
href="http://srfi.schemers.org/">SRFI</a> (Scheme request for
implementation) process for proposing extensions for the programming
language Scheme.
<p>Finally, Python has a similar mechanism: <a
href="http://python.sourceforge.net/peps/">PEPs</a> (Python extension
proposal).
<hr>
<a href="http://www.complang.tuwien.ac.at/anton/">Anton Ertl</a>
</body></html>