Path: csiph.com!usenet.pasdenom.info!aioe.org!rt.uk.eu.org!weretis.net!feeder1.news.weretis.net!news.szaf.org!news.gnuher.de!rz.uni-karlsruhe.de!feed.news.schlund.de!schlund.de!news.online.de!not-for-mail From: Bernd Paysan Newsgroups: comp.lang.forth Subject: Re: RfD: Interpret S\" (Version 2) Date: Wed, 12 Mar 2014 12:51:21 +0100 Organization: 1&1 Internet AG Lines: 15 Message-ID: References: <43003c26-3103-4a1e-820a-f633d9196aab@googlegroups.com> NNTP-Posting-Host: p5dcd6afa.dip0.t-ipconnect.de Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Trace: online.de 1394625081 9132 93.205.106.250 (12 Mar 2014 11:51:21 GMT) X-Complaints-To: abuse@einsundeins.com NNTP-Posting-Date: Wed, 12 Mar 2014 11:51:21 +0000 (UTC) User-Agent: KNode/4.11.5 Xref: csiph.com comp.lang.forth:29024 Mark Wills wrote: > Meh. Why not just bite the bullet: Define interpretation semantics for S". > That would be *far* more useful, since it's in core. Then assert that S\" > interpretation semantics are that of S" and be done with it. Oh, Mark, we already do that. Well, the interpretation semantics is in the file wordset, just as with S\". And of course S\"'s interpretation semantic differs from S"'s by interpreting \. -- Bernd Paysan "If you want it done right, you have to do it yourself" http://bernd-paysan.de/