Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #29030
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: RfD: Interpret S\" (Version 2) |
| Date | 2014-03-12 19:43 +0100 |
| Organization | 1&1 Internet AG |
| Message-ID | <lfq9sj$ja$1@online.de> (permalink) |
| References | (1 earlier) <lfnl3l$7su$1@dont-email.me> <43003c26-3103-4a1e-820a-f633d9196aab@googlegroups.com> <lfphnp$8tc$1@online.de> <22adc819-3a40-4ad8-a3b6-a1c4b89f3ac2@googlegroups.com> <1eimfh44wt6f8.fed8gv2av91p$.dlg@40tude.net> |
Coos Haak wrote: > 6.1.2165 S" is in CORE and compilation semantics only but 11.6.1.2165 S" > is in FILE ACCESS and has interpretation semantics. > You lose EUR 0,02 ;( And that's what he asks for is just what we do: Specify the interpretation semantics of S" and S\", specify where the strings go (in now at least two string buffers with at least 80 characters each), etc.. I was about to suggest adding a cross reference, but of course there already is one. FWIW, while we are at changing S" and S\": For all those maybe-state-smart words (or however they are implemented), which have different interpretation and compilation semantics, there must be a "Note: An ambiguous condition exists if any of POSTPONE, [COMPILE], ’ or [’] are applied to <word>." boilerplate before the cross-reference line (just as for TO). -- Bernd Paysan "If you want it done right, you have to do it yourself" http://bernd-paysan.de/
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
RfD: Interpret S\" (Version 2) "Peter Knaggs" <pjk@bcs.org.uk> - 2014-03-11 11:18 +0000
Re: RfD: Interpret S\" (Version 2) "Alex McDonald" <blog@rivadpm.com> - 2014-03-11 18:36 +0000
Re: RfD: Interpret S\" (Version 2) Bernd Paysan <bernd.paysan@gmx.de> - 2014-03-11 21:32 +0100
Re: RfD: Interpret S\" (Version 2) "Alex McDonald" <blog@rivadpm.com> - 2014-03-11 22:38 +0000
Re: RfD: Interpret S\" (Version 2) Bernd Paysan <bernd.paysan@gmx.de> - 2014-03-12 13:02 +0100
Re: RfD: Interpret S\" (Version 2) Andrew Haley <andrew29@littlepinkcloud.invalid> - 2014-03-12 04:41 -0500
Re: RfD: Interpret S\" (Version 2) Bernd Paysan <bernd.paysan@gmx.de> - 2014-03-12 13:16 +0100
Re: RfD: Interpret S\" (Version 2) Mark Wills <markwills1970@gmail.com> - 2014-03-12 04:33 -0700
Re: RfD: Interpret S\" (Version 2) Bernd Paysan <bernd.paysan@gmx.de> - 2014-03-12 12:51 +0100
Re: RfD: Interpret S\" (Version 2) Mark Wills <markwills1970@gmail.com> - 2014-03-12 06:25 -0700
Re: RfD: Interpret S\" (Version 2) Coos Haak <chforth@hccnet.nl> - 2014-03-12 15:59 +0100
Re: RfD: Interpret S\" (Version 2) Bernd Paysan <bernd.paysan@gmx.de> - 2014-03-12 19:43 +0100
Re: RfD: Interpret S\" (Version 2) "Peter Knaggs" <pjk@bcs.org.uk> - 2014-03-13 18:55 +0000
csiph-web