Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #58987 > unrolled thread
| Started by | lehs <skydda.barnen@gmail.com> |
|---|---|
| First post | 2017-05-10 08:21 -0700 |
| Last post | 2017-05-15 11:23 +0000 |
| Articles | 20 on this page of 215 — 25 participants |
Back to article view | Back to comp.lang.forth
Would ?EXIT work in all ANS-Forth systems? lehs <skydda.barnen@gmail.com> - 2017-05-10 08:21 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-10 16:39 +0100
Re: Would ?EXIT work in all ANS-Forth systems? lehs <skydda.barnen@gmail.com> - 2017-05-10 08:46 -0700
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-10 16:04 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-11 04:22 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-11 10:35 +0100
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-11 05:08 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Julian Fondren <julian.fondren@gmail.com> - 2017-05-11 03:51 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-11 07:02 -0500
Re: Would ?EXIT work in all ANS-Forth systems? rickman <gnuarm@gmail.com> - 2017-05-13 11:55 -0400
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-15 09:32 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Cecil Bayona <cbayona@cbayona.com> - 2017-05-15 11:56 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-15 12:20 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Cecil Bayona <cbayona@cbayona.com> - 2017-05-15 12:31 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-15 15:50 -0500
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-10 16:49 +0000
Re: Would ?EXIT work in all ANS-Forth systems? lehs <skydda.barnen@gmail.com> - 2017-05-10 12:04 -0700
Re: Would ?EXIT work in all ANS-Forth systems? humptydumpty <ouatubi@gmail.com> - 2017-05-11 01:08 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-11 09:13 +0100
Re: Would ?EXIT work in all ANS-Forth systems? humptydumpty <ouatubi@gmail.com> - 2017-05-11 01:48 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-11 09:59 +0100
Re: Would ?EXIT work in all ANS-Forth systems? "Rudy Velthuis" <newsgroups@rvelthuis.de> - 2017-05-12 14:20 +0000
Re: Would ?EXIT work in all ANS-Forth systems? lehs <skydda.barnen@gmail.com> - 2017-05-12 17:01 -0700
Re: Would ?EXIT work in all ANS-Forth systems? humptydumpty <ouatubi@gmail.com> - 2017-05-12 22:18 -0700
Re: Would ?EXIT work in all ANS-Forth systems? lehs <skydda.barnen@gmail.com> - 2017-05-13 03:09 -0700
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-05-13 21:07 +1000
Re: Would ?EXIT work in all ANS-Forth systems? "Rudy Velthuis" <newsgroups@rvelthuis.de> - 2017-05-13 14:20 +0000
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-05-14 11:59 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-14 09:21 -0500
Re: Would ?EXIT work in all ANS-Forth systems? humptydumpty <ouatubi@gmail.com> - 2017-05-14 10:43 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-14 18:35 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Lars Brinkhoff <lars.spam@nocrew.org> - 2017-05-15 07:11 +0200
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-15 04:35 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Julian Fondren <julian.fondren@gmail.com> - 2017-05-15 03:54 -0700
Re: Would ?EXIT work in all ANS-Forth systems? mhx@iae.nl - 2017-05-15 04:07 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-15 06:23 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Julian Fondren <julian.fondren@gmail.com> - 2017-05-15 06:53 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-15 09:18 -0500
Re: Would ?EXIT work in all ANS-Forth systems? humptydumpty <ouatubi@gmail.com> - 2017-05-14 22:44 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-15 04:16 -0500
Re: Would ?EXIT work in all ANS-Forth systems? humptydumpty <ouatubi@gmail.com> - 2017-05-16 02:00 -0700
Re: Would ?EXIT work in all ANS-Forth systems? humptydumpty <ouatubi@gmail.com> - 2017-05-16 02:43 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-16 05:08 -0500
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-16 12:11 +0000
Re: Would ?EXIT work in all ANS-Forth systems? NN <november.nihal@gmail.com> - 2017-05-17 05:24 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-17 07:35 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-17 14:59 +0100
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-17 13:30 +0000
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-05-15 11:09 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Raimond Dragomir <raimond.dragomir@gmail.com> - 2017-05-14 21:17 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Lars Brinkhoff <lars.spam@nocrew.org> - 2017-05-15 07:13 +0200
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-05-16 10:24 +1000
Re: Would ?EXIT work in all ANS-Forth systems? humptydumpty <ouatubi@gmail.com> - 2017-05-16 01:13 -0700
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-16 12:26 +0000
Re: Would ?EXIT work in all ANS-Forth systems? humptydumpty <ouatubi@gmail.com> - 2017-05-17 01:58 -0700
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-17 16:45 +0000
Re: Would ?EXIT work in all ANS-Forth systems? obi65537@gmail.com - 2017-05-25 12:04 -0700
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-26 10:02 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-26 07:46 -0500
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-26 13:53 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-26 10:14 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Cecil Bayona <cbayona@cbayona.com> - 2017-05-26 10:16 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Raimond Dragomir <raimond.dragomir@gmail.com> - 2017-05-26 08:59 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Cecil Bayona <cbayona@cbayona.com> - 2017-05-26 11:27 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Raimond Dragomir <raimond.dragomir@gmail.com> - 2017-05-26 10:19 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Lars Brinkhoff <lars.spam@nocrew.org> - 2017-05-26 20:20 +0200
Re: Would ?EXIT work in all ANS-Forth systems? Raimond Dragomir <raimond.dragomir@gmail.com> - 2017-05-26 21:38 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Cecil Bayona <cbayona@cbayona.com> - 2017-05-26 14:06 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Raimond Dragomir <raimond.dragomir@gmail.com> - 2017-05-26 22:00 -0700
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-26 17:06 +0000
Re: Would ?EXIT work in all ANS-Forth systems? hum9 <obi65537@gmail.com> - 2017-05-27 01:15 -0700
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-28 14:17 +0000
Re: Would ?EXIT work in all ANS-Forth systems? obi65537@gmail.com - 2017-05-29 20:30 -0700
Re: Would ?EXIT work in all ANS-Forth systems? hum9 <obi65537@gmail.com> - 2017-05-29 21:08 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-30 04:12 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-30 12:44 +0100
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-30 08:09 -0500
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-30 14:35 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-30 16:27 +0100
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-31 12:16 -0500
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-06-01 05:34 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-06-01 02:14 -0500
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-06-01 08:40 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-06-01 06:14 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-06-01 13:16 +0100
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-06-01 07:43 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-06-01 14:15 +0100
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-06-02 11:49 +0100
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-06-01 16:42 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-06-02 03:19 -0500
Re: Would ?EXIT work in all ANS-Forth systems? hughaguilar96@gmail.com - 2017-06-01 14:07 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Matthias Trute <matthias.trute@gmail.com> - 2017-06-02 12:26 -0700
Re: Would ?EXIT work in all ANS-Forth systems? minforth@arcor.de - 2017-06-02 13:16 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Matthias Trute <matthias.trute@gmail.com> - 2017-06-03 01:34 -0700
Re: Would ?EXIT work in all ANS-Forth systems? minforth@arcor.de - 2017-06-03 02:54 -0700
Re: Would ?EXIT work in all ANS-Forth systems? hughaguilar96@gmail.com - 2017-06-01 13:53 -0700
Re: Would ?EXIT work in all ANS-Forth systems? hughaguilar96@gmail.com - 2017-06-01 13:48 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-06-01 22:31 +0100
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-06-02 08:03 -0500
Re: Would ?EXIT work in all ANS-Forth systems? albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-06-02 15:16 +0200
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-06-02 14:30 +0100
Re: Would ?EXIT work in all ANS-Forth systems? hughaguilar96@gmail.com - 2017-06-02 07:32 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-06-02 18:23 +0100
Re: Would ?EXIT work in all ANS-Forth systems? Julian Fondren <julian.fondren@gmail.com> - 2017-06-01 14:49 -0700
Re: Would ?EXIT work in all ANS-Forth systems? minforth@arcor.de - 2017-06-01 16:05 -0700
Re: Would ?EXIT work in all ANS-Forth systems? hughaguilar96@gmail.com - 2017-06-01 17:48 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Julian Fondren <julian.fondren@gmail.com> - 2017-06-01 18:44 -0700
Re: Would ?EXIT work in all ANS-Forth systems? hughaguilar96@gmail.com - 2017-06-01 19:14 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Julian Fondren <julian.fondren@gmail.com> - 2017-06-01 19:54 -0700
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-27 17:40 +0000
WRAP...END-WRAP (was: Would ?EXIT work ...) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-30 15:28 +0000
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-05-24 15:46 +1000
Re: Would ?EXIT work in all ANS-Forth systems? humptydumpty <obi65537@gmail.com> - 2017-05-25 11:51 -0700
Re: Would ?EXIT work in all ANS-Forth systems? humptydumpty <obi65537@gmail.com> - 2017-05-25 20:38 -0700
Re: Would ?EXIT work in all ANS-Forth systems? obi65537@gmail.com - 2017-05-25 22:03 -0700
Re: Would ?EXIT work in all ANS-Forth systems? obi65537@gmail.com - 2017-05-25 22:09 -0700
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-05-26 21:56 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-26 13:30 +0100
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-05-27 15:04 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-27 17:33 +0100
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-05-29 12:17 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-29 08:42 +0100
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-05-30 11:14 +1000
Re: Would ?EXIT work in all ANS-Forth systems? obi65537@gmail.com - 2017-05-29 20:32 -0700
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-05-30 14:40 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-30 12:55 +0100
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-05-31 12:17 +1000
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-06-01 12:01 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-06-01 02:17 -0500
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-06-01 22:09 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-06-01 07:51 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-06-01 14:20 +0100
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-06-02 13:09 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-06-02 08:44 +0100
Re: Would ?EXIT work in all ANS-Forth systems? obi65537@gmail.com - 2017-06-02 11:05 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-06-02 19:34 +0100
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-06-03 14:29 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Julian Fondren <julian.fondren@gmail.com> - 2017-06-02 21:54 -0700
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-06-04 22:52 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Julian Fondren <julian.fondren@gmail.com> - 2017-06-02 22:24 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2017-06-03 07:34 +0100
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-06-03 08:39 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2017-06-03 13:47 +0100
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-06-03 14:36 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2017-06-04 17:29 +0100
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-06-04 10:28 +0100
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-06-05 15:09 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-06-05 09:36 +0100
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-06-05 09:35 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-06-05 10:57 +0100
Re: Would ?EXIT work in all ANS-Forth systems? JennyB <jennybrien@googlemail.com> - 2017-06-05 13:07 -0700
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-06-07 12:42 +1000
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-06-05 20:07 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-06-04 10:45 +0100
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-06-05 19:21 +1000
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-06-03 14:19 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-06-02 03:32 -0500
Re: Would ?EXIT work in all ANS-Forth systems? hughaguilar96@gmail.com - 2017-06-02 06:50 -0700
Re: Would ?EXIT work in all ANS-Forth systems? hum9 <obi65537@gmail.com> - 2017-05-27 00:33 -0700
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-05-27 14:53 +1000
READ-FILE over-specified? "HAA" <someone@microsoft.com> - 2017-05-27 21:28 +1000
Re: READ-FILE over-specified? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-27 13:11 +0000
Re: READ-FILE over-specified? "HAA" <someone@microsoft.com> - 2017-05-29 13:47 +1000
Re: READ-FILE over-specified? hughaguilar96@gmail.com - 2017-05-28 21:58 -0700
Re: READ-FILE over-specified? "HAA" <someone@microsoft.com> - 2017-05-30 11:06 +1000
Re: READ-FILE over-specified? albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-05-28 09:44 +0200
Re: READ-FILE over-specified? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-28 13:41 +0000
Re: READ-FILE over-specified? albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-05-28 19:59 +0200
Re: READ-FILE over-specified? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-29 05:20 +0000
Re: READ-FILE over-specified? albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-05-29 10:29 +0200
Re: READ-FILE over-specified? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-29 09:34 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2017-05-16 09:42 +0100
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-16 09:53 +0100
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-16 04:53 -0500
Re: Would ?EXIT work in all ANS-Forth systems? albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-05-16 12:32 +0200
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-16 12:35 +0100
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-16 10:48 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-16 18:23 +0100
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-17 04:33 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-17 12:29 +0100
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-16 10:28 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-16 10:43 -0500
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-16 16:34 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-16 12:41 -0500
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-17 16:14 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-18 03:05 -0500
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-18 16:33 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-18 12:43 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-18 04:01 -0500
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-18 15:41 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-18 11:58 -0500
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-18 22:57 +0100
Re: Would ?EXIT work in all ANS-Forth systems? "HAA" <someone@microsoft.com> - 2017-05-17 00:32 +1000
Re: Would ?EXIT work in all ANS-Forth systems? Alex <alex@rivadpm.com> - 2017-05-16 15:53 +0100
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-15 05:29 +0000
Re: Would ?EXIT work in all ANS-Forth systems? humptydumpty <ouatubi@gmail.com> - 2017-05-14 23:00 -0700
Re: Would ?EXIT work in all ANS-Forth systems? rickman <gnuarm@gmail.com> - 2017-05-17 12:27 -0400
Re: Would ?EXIT work in all ANS-Forth systems? "Rudy Velthuis" <newsgroups@rvelthuis.de> - 2017-05-15 09:16 +0000
Re: Would ?EXIT work in all ANS-Forth systems? "Rudy Velthuis" <newsgroups@rvelthuis.de> - 2017-05-15 09:55 +0000
Re: Would ?EXIT work in all ANS-Forth systems? "Rudy Velthuis" <newsgroups@rvelthuis.de> - 2017-05-13 14:25 +0000
Re: Would ?EXIT work in all ANS-Forth systems? Julian Fondren <julian.fondren@gmail.com> - 2017-05-13 07:49 -0700
Re: Would ?EXIT work in all ANS-Forth systems? "Rudy Velthuis" <newsgroups@rvelthuis.de> - 2017-05-15 09:59 +0000
Re: Would ?EXIT work in all ANS-Forth systems? "Rudy Velthuis" <newsgroups@rvelthuis.de> - 2017-05-15 12:22 +0000
Re: Would ?EXIT work in all ANS-Forth systems? "Rudy Velthuis" <newsgroups@rvelthuis.de> - 2017-05-13 14:19 +0000
Re: Would ?EXIT work in all ANS-Forth systems? lehs <skydda.barnen@gmail.com> - 2017-05-14 23:23 -0700
Re: Would ?EXIT work in all ANS-Forth systems? Raimond Dragomir <raimond.dragomir@gmail.com> - 2017-05-15 00:10 -0700
Re: Would ?EXIT work in all ANS-Forth systems? anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-15 09:35 +0000
Re: Would ?EXIT work in all ANS-Forth systems? lehs <skydda.barnen@gmail.com> - 2017-05-15 00:54 -0700
Return-address manipulation (was: Would ?EXIT ...) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-15 08:47 +0000
Re: Return-address manipulation (was: Would ?EXIT ...) stephen@mpeforth.com (Stephen Pelc) - 2017-05-15 11:53 +0000
Re: Return-address manipulation (was: Would ?EXIT ...) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-16 13:03 +0000
Re: Return-address manipulation (was: Would ?EXIT ...) Raimond Dragomir <raimond.dragomir@gmail.com> - 2017-05-16 07:06 -0700
Re: Return-address manipulation (was: Would ?EXIT ...) Raimond Dragomir <raimond.dragomir@gmail.com> - 2017-05-16 07:14 -0700
Re: Would ?EXIT work in all ANS-Forth systems? "Elizabeth D. Rather" <erather@forth.com> - 2017-05-14 21:58 -1000
Re: Would ?EXIT work in all ANS-Forth systems? stephen@mpeforth.com (Stephen Pelc) - 2017-05-15 11:23 +0000
Page 8 of 11 — ← Prev page 1 … 6 7 [8] 9 10 11 Next page →
| From | Gerry Jackson <gerry@jackson9000.fsnet.co.uk> |
|---|---|
| Date | 2017-06-03 07:34 +0100 |
| Message-ID | <ogtl2c$hih$1@dont-email.me> |
| In reply to | #60215 |
On 03/06/2017 05:29, HAA wrote: > Alex wrote: >> ... >> At the risk of pissing you off even more, I'll repeat; you and HAA are >> proposing UNNEST instead of THROW; it's not me proposing THROW instead >> of UNNEST. It's up to you to justify UNNEST, not me. > You've been given two examples using UNNEST. Don't "piss off" readers with > posts intended to obfuscate and wear out. Make good on your claim CATCH/ > THROW can do everything UNNEST can by rewriting those two examples. > When you've done that, I'll be happy to compare them and readers can decide > for themselves whether UNNEST is justified for them. > >> And, as it stands, >> neither you nor s/he have shown how it's possible to write such a word >> in a standard way. > It's not my job to make things standard. That's the role of TC's. That doesn't answer Alex's question which was how to write UNNEST using standard words. > > In the absence of CATCH/THROW alternatives, let's compare the only alternative > to UNNEST presented thus far. To throw another dog into the fight, there's something I posted on 3 June 2015 as a lightweight CATCH/THROW https://groups.google.com/forum/#!topic/comp.lang.forth/b0rpNOd8WF8%5B76-100%5D See the 6th message -- Gerry
[toc] | [prev] | [next] | [standalone]
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2017-06-03 08:39 +0000 |
| Message-ID | <2017Jun3.103947@mips.complang.tuwien.ac.at> |
| In reply to | #60218 |
Gerry Jackson <gerry@jackson9000.fsnet.co.uk> writes:
>To throw another dog into the fight, there's something I posted on 3
>June 2015 as a lightweight CATCH/THROW
>
>https://groups.google.com/forum/#!topic/comp.lang.forth/b0rpNOd8WF8%5B76-100%5D
>
>See the 6th message
Please post the Message-ID; you can provide groups.google links in
addition for people who prefer that, but the Message-Id is the Usenet
way to refer to a message, and works with all NNTP servers and some
archive sites.
- anton
--
M. Anton Ertl http://www.complang.tuwien.ac.at/anton/home.html
comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html
New standard: http://www.forth200x.org/forth200x.html
EuroForth 2017: http://www.euroforth.org/ef17/
[toc] | [prev] | [next] | [standalone]
| From | Gerry Jackson <gerry@jackson9000.fsnet.co.uk> |
|---|---|
| Date | 2017-06-03 13:47 +0100 |
| Message-ID | <oguatu$hds$1@dont-email.me> |
| In reply to | #60220 |
On 03/06/2017 09:39, Anton Ertl wrote: > Gerry Jackson <gerry@jackson9000.fsnet.co.uk> writes: >> To throw another dog into the fight, there's something I posted on 3 >> June 2015 as a lightweight CATCH/THROW >> >> https://groups.google.com/forum/#!topic/comp.lang.forth/b0rpNOd8WF8%5B76-100%5D >> >> See the 6th message > > Please post the Message-ID; you can provide groups.google links in > addition for people who prefer that, but the Message-Id is the Usenet > way to refer to a message, and works with all NNTP servers and some > archive sites. > > - anton > Message-ID: <mdc4da$kte$1@dont-email.me> if that's the one you want. -- Gerry
[toc] | [prev] | [next] | [standalone]
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2017-06-03 14:36 +0000 |
| Message-ID | <2017Jun3.163615@mips.complang.tuwien.ac.at> |
| In reply to | #60224 |
Gerry Jackson <gerry@jackson9000.fsnet.co.uk> writes:
>Message-ID: <mdc4da$kte$1@dont-email.me>
>
>if that's the one you want.
Yes, thank you. Here's how I get it from my NNTP server:
[~:94568] telnet news.eternal-september.org nntp
Trying 213.239.209.88...
Connected to news.eternal-september.org.
Escape character is '^]'.
200 news.eternal-september.org InterNetNews NNRP server INN 2.7.0 (20170224 snapshot) ready (posting ok)
authinfo user <userid>
381 Enter password
authinfo pass <password>
281 Authentication succeeded
article <mdc4da$kte$1@dont-email.me>
220 0 <mdc4da$kte$1@dont-email.me> article
Path: eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Gerry Jackson <gerry@jackson9000.fsnet.co.uk>
Newsgroups: comp.lang.forth
Subject: Re: The Declarative, Imperative, then Inquisitive Pattern
Date: Fri, 06 Mar 2015 11:53:01 +0000
...
I indented the output so that you can more easily see the input
- anton
--
M. Anton Ertl http://www.complang.tuwien.ac.at/anton/home.html
comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html
New standard: http://www.forth200x.org/forth200x.html
EuroForth 2017: http://www.euroforth.org/ef17/
[toc] | [prev] | [next] | [standalone]
| From | Gerry Jackson <gerry@jackson9000.fsnet.co.uk> |
|---|---|
| Date | 2017-06-04 17:29 +0100 |
| Message-ID | <oh1ca1$o6k$1@dont-email.me> |
| In reply to | #60232 |
On 03/06/2017 15:36, Anton Ertl wrote: > Gerry Jackson <gerry@jackson9000.fsnet.co.uk> writes: >> Message-ID: <mdc4da$kte$1@dont-email.me> >> >> if that's the one you want. > > Yes, thank you. Here's how I get it from my NNTP server: > > [~:94568] telnet news.eternal-september.org nntp > Trying 213.239.209.88... > Connected to news.eternal-september.org. > Escape character is '^]'. > 200 news.eternal-september.org InterNetNews NNRP server INN 2.7.0 (20170224 snapshot) ready (posting ok) > authinfo user <userid> > 381 Enter password > authinfo pass <password> > 281 Authentication succeeded > article <mdc4da$kte$1@dont-email.me> > 220 0 <mdc4da$kte$1@dont-email.me> article > Path: eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail > From: Gerry Jackson <gerry@jackson9000.fsnet.co.uk> > Newsgroups: comp.lang.forth > Subject: Re: The Declarative, Imperative, then Inquisitive Pattern > Date: Fri, 06 Mar 2015 11:53:01 +0000 > ... > > I indented the output so that you can more easily see the input > Thank you for that information. I use Thunderbird which hides that lower level stuff from me. Message-ID's look like an email address to Thunderbird. -- Gerry
[toc] | [prev] | [next] | [standalone]
| From | Alex <alex@rivadpm.com> |
|---|---|
| Date | 2017-06-04 10:28 +0100 |
| Message-ID | <oh0jkk$7i9$1@dont-email.me> |
| In reply to | #60218 |
On 6/3/2017 07:34, Gerry Jackson wrote: > On 03/06/2017 05:29, HAA wrote: >> Alex wrote: >>> ... >>> At the risk of pissing you off even more, I'll repeat; you and HAA are >>> proposing UNNEST instead of THROW; it's not me proposing THROW instead >>> of UNNEST. It's up to you to justify UNNEST, not me. >> You've been given two examples using UNNEST. Don't "piss off" readers >> with >> posts intended to obfuscate and wear out. Make good on your claim >> CATCH/ >> THROW can do everything UNNEST can by rewriting those two examples. >> When you've done that, I'll be happy to compare them and readers can >> decide >> for themselves whether UNNEST is justified for them. >> >>> And, as it stands, >>> neither you nor s/he have shown how it's possible to write such a word >>> in a standard way. >> It's not my job to make things standard. That's the role of TC's. > > That doesn't answer Alex's question which was how to write UNNEST using > standard words. > >> >> In the absence of CATCH/THROW alternatives, let's compare the only >> alternative >> to UNNEST presented thus far. > > To throw another dog into the fight, there's something I posted on 3 > June 2015 as a lightweight CATCH/THROW > > https://groups.google.com/forum/#!topic/comp.lang.forth/b0rpNOd8WF8%5B76-100%5D > > > See the 6th message > I read the rest of the thread, and it reminded me that I've been here before with this argument. -- Alex
[toc] | [prev] | [next] | [standalone]
| From | "HAA" <someone@microsoft.com> |
|---|---|
| Date | 2017-06-05 15:09 +1000 |
| Message-ID | <oh2p2t$1pnb$1@gioia.aioe.org> |
| In reply to | #60218 |
Gerry Jackson wrote:
> On 03/06/2017 05:29, HAA wrote:
> > Alex wrote:
> >> ...
> >> At the risk of pissing you off even more, I'll repeat; you and HAA are
> >> proposing UNNEST instead of THROW; it's not me proposing THROW instead
> >> of UNNEST. It's up to you to justify UNNEST, not me.
> > You've been given two examples using UNNEST. Don't "piss off" readers with
> > posts intended to obfuscate and wear out. Make good on your claim CATCH/
> > THROW can do everything UNNEST can by rewriting those two examples.
> > When you've done that, I'll be happy to compare them and readers can decide
> > for themselves whether UNNEST is justified for them.
> >
> >> And, as it stands,
> >> neither you nor s/he have shown how it's possible to write such a word
> >> in a standard way.
> > It's not my job to make things standard. That's the role of TC's.
>
> That doesn't answer Alex's question which was how to write UNNEST using
> standard words.
I answered it. Matters pertaining to standards is a matter for the TC's.
I know of no TC that has rejected a word on the grounds it couldn't be written
portably. Take TRAVERSE-WORDLIST for example, which Alex himself proposed:
"Implementation of TRAVERSE-WORDLIST requires carnal knowledge
of the structure of the wordlist."
[toc] | [prev] | [next] | [standalone]
| From | Alex <alex@rivadpm.com> |
|---|---|
| Date | 2017-06-05 09:36 +0100 |
| Message-ID | <oh34vc$nle$1@dont-email.me> |
| In reply to | #60318 |
On 6/5/2017 06:09, HAA wrote: > Gerry Jackson wrote: >> On 03/06/2017 05:29, HAA wrote: >>> Alex wrote: >>>> ... >>>> At the risk of pissing you off even more, I'll repeat; you and HAA are >>>> proposing UNNEST instead of THROW; it's not me proposing THROW instead >>>> of UNNEST. It's up to you to justify UNNEST, not me. >>> You've been given two examples using UNNEST. Don't "piss off" readers with >>> posts intended to obfuscate and wear out. Make good on your claim CATCH/ >>> THROW can do everything UNNEST can by rewriting those two examples. >>> When you've done that, I'll be happy to compare them and readers can decide >>> for themselves whether UNNEST is justified for them. >>> >>>> And, as it stands, >>>> neither you nor s/he have shown how it's possible to write such a word >>>> in a standard way. >>> It's not my job to make things standard. That's the role of TC's. >> >> That doesn't answer Alex's question which was how to write UNNEST using >> standard words. > > I answered it. Matters pertaining to standards is a matter for the TC's. > > I know of no TC that has rejected a word on the grounds it couldn't be written > portably. Take TRAVERSE-WORDLIST for example, which Alex himself proposed: > > "Implementation of TRAVERSE-WORDLIST requires carnal knowledge > of the structure of the wordlist." > So UNNEST requires carnal knowledge. Here's a proposed wording for it; UNNEST Remove a level of nesting. Interpretation: Interpretation semantics for this word are undefined. Execution: ( -- ) ( R: nest-sys3 nest-sys2 nest-sys1 -- R: ) Return control to the calling definition specified by nest-sys3. Before executing UNNEST within a do-loop, a program shall discard the loop-control parameters by executing UNLOOP. An ambiguous condition exists if the nest-sys parameters are unavailable, or any other entries are on the return stack between nest-sys3 and nest-sys1 when UNNEST is executed. Rationale: Chuck Moore once mentioned it. Typical implementations: : UNNEST POSTPONE R> POSTPONE DROP POSTPONE EXIT ; IMMEDIATE : UNNEST 2R> 2DROP ; I leave the rest of this to you. -- Alex
[toc] | [prev] | [next] | [standalone]
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2017-06-05 09:35 +0000 |
| Message-ID | <2017Jun5.113500@mips.complang.tuwien.ac.at> |
| In reply to | #60327 |
Alex <alex@rivadpm.com> writes:
>So UNNEST requires carnal knowledge. Here's a proposed wording for it;
>
>UNNEST
>
>Remove a level of nesting.
>
>Interpretation:
>Interpretation semantics for this word are undefined.
>
>Execution:
>( -- ) ( R: nest-sys3 nest-sys2 nest-sys1 -- R: )
>
>Return control to the calling definition specified by nest-sys3. Before
>executing UNNEST within a do-loop, a program shall discard the
>loop-control parameters by executing UNLOOP. An ambiguous condition
>exists if the nest-sys parameters are unavailable, or any other entries
>are on the return stack between nest-sys3 and nest-sys1 when UNNEST is
>executed.
What about locals?
- anton
--
M. Anton Ertl http://www.complang.tuwien.ac.at/anton/home.html
comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html
New standard: http://www.forth200x.org/forth200x.html
EuroForth 2017: http://www.euroforth.org/ef17/
[toc] | [prev] | [next] | [standalone]
| From | Alex <alex@rivadpm.com> |
|---|---|
| Date | 2017-06-05 10:57 +0100 |
| Message-ID | <oh39n0$74n$1@dont-email.me> |
| In reply to | #60331 |
On 6/5/2017 10:35, Anton Ertl wrote: > Alex <alex@rivadpm.com> writes: >> So UNNEST requires carnal knowledge. Here's a proposed wording for it; >> >> UNNEST >> >> Remove a level of nesting. >> >> Interpretation: >> Interpretation semantics for this word are undefined. >> >> Execution: >> ( -- ) ( R: nest-sys3 nest-sys2 nest-sys1 -- R: ) >> >> Return control to the calling definition specified by nest-sys3. Before >> executing UNNEST within a do-loop, a program shall discard the >> loop-control parameters by executing UNLOOP. An ambiguous condition >> exists if the nest-sys parameters are unavailable, or any other entries >> are on the return stack between nest-sys3 and nest-sys1 when UNNEST is >> executed. > > What about locals? Not my problem. -- Alex
[toc] | [prev] | [next] | [standalone]
| From | JennyB <jennybrien@googlemail.com> |
|---|---|
| Date | 2017-06-05 13:07 -0700 |
| Message-ID | <d2d3d47f-a536-4a25-b736-f7ecd119b3af@googlegroups.com> |
| In reply to | #60334 |
Isn't it the case that any factor which uses UNNEST might equally well be written as a ]] ... [[ macro with ?EXIT or IF ... EXIT THEN ? Let's try Samuel Falvo's Row example: SF: This time, however, I wanted to re-implement row using definitions of similar structure to those using row itself, for I had discovered that using row in other definitions proved remarkably easy, and made for very readable code. I started with the most obvious use-case: I knew that if a row wasn’t found in the DLCS table, we had to return a zero to the caller of whatever word invoked row (remember: row cannot itself return without having a valid record number as its result). : row -found 2drop 0 r> drop ; Becomes: : row ]] -found IF 2DROP 0 EXIT THEN [[ ; IMMEDIATE SF: Notice the structure of the aforementioned definition. -found, taken otherwise completely out of context, states a fact or pre-condition about the code which follows, which the reader safely assumes must hold for all subsequent code. Hence, 2drop 0 r> drop executes with full confidence that the record sought is genuinely not in the database. Me: 2DROP 0 executes and the rest of the definition that follows the call to Row is skipped. SF: Eventually, I had to implement -found. Once again, I decided to engineer the code so that it stated only facts, without obvious concern to what would happen had these facts been wrong: : -found 0 begin dup nextDlc @ < while -match cell+ repeat drop ; For those not familiar with idiomatic Forth coding conventions, I defined -found to mean, literally, for all allocated records in the table, no match exists. Note that -found, while itself a declaration, also makes use of another declaration: -match. cell+ runs with full confidence that no match has been discovered thus far. : -match hit? if nip nip r> r> 2drop exit then ; -match ensures that no match (“hit”) exists insofar as it concerns -found and row. What happens, though, if it discovers a match? Considering the context we’ve established so far, we cannot just return to the caller because the caller’s subsequent code depends on there not being any match! Likewise, we cannot return to the word who called row’s caller. Only returning to the word which called row itself remains, making sure we also return the record number we promised for subsequent code to use. Me: I found this skipping of two levels very confusing, so my version of -Found returns a flag for use by Row: : -found ( -- t | row# f ) 0 begin dup nextDlc @ < while -match cell+ repeat drop TRUE ; : -match ]] hit? if nip nip FALSE exit then [[ ; IMMEDIATE
[toc] | [prev] | [next] | [standalone]
| From | "HAA" <someone@microsoft.com> |
|---|---|
| Date | 2017-06-07 12:42 +1000 |
| Message-ID | <oh7p8q$1tli$1@gioia.aioe.org> |
| In reply to | #60359 |
JennyB wrote: > Isn't it the case that any factor which uses UNNEST might equally well be written as a > ]] ... [[ macro with ?EXIT or IF ... EXIT THEN ? > > Let's try Samuel Falvo's Row example: > ... > > : -match hit? if nip nip unnest unnest then ; > : -found 0 begin dup nextDlc @ < while -match cell+ repeat drop ; > : row -found 2drop 0 unnest ; > > Becomes: > > : -match ]] hit? if nip nip FALSE exit then [[ ; IMMEDIATE > : -found ( -- t | row# f ) 0 begin dup nextDlc @ < while -match cell+ repeat drop TRUE ; > : row ]] -found IF 2DROP 0 EXIT THEN [[ ; IMMEDIATE To me, the first still looks simpler and cleaner. And you get to keep the small code footprint. I'd put UNNEST in the same category as UNLOOP i.e. while you can always avoid it, doing so will come at a cost.
[toc] | [prev] | [next] | [standalone]
| From | "HAA" <someone@microsoft.com> |
|---|---|
| Date | 2017-06-05 20:07 +1000 |
| Message-ID | <oh3afg$lpa$1@gioia.aioe.org> |
| In reply to | #60331 |
Anton Ertl wrote: > > What about locals? > > - anton "ambiguous condition" Anyone who uses locals in Forth deserves the mess locals create. Alex wrote: > ... > Rationale: > Chuck Moore once mentioned it. > ... > I leave the rest of this to you. No thanks. Whether it's Chuck Moore or the Standard telling you to implement something, is the worst reason for having it.
[toc] | [prev] | [next] | [standalone]
| From | Alex <alex@rivadpm.com> |
|---|---|
| Date | 2017-06-04 10:45 +0100 |
| Message-ID | <oh0kl0$ap3$1@dont-email.me> |
| In reply to | #60215 |
On 6/3/2017 05:29, HAA wrote: >> And, as it stands, >> neither you nor s/he have shown how it's possible to write such a word >> in a standard way. > It's not my job to make things standard. That's the role of TC's. To resolve the ambiguity, I'll rephrase it as "write such a word with standard words". As to standardization of such a word, it might be possible. But it would require a lot of support, since as Julian Fondren has shown, your example code met a commercial & well respected Forth compiler that did tail-call elimination, and you didn't test your code, and your code failed to work as advertised. I'm not adding any more to the discussion; as Gerry Jackson reminded me ( https://groups.google.com/forum/#!topic/comp.lang.forth/b0rpNOd8WF8%5B76-100%5D), we've been here before and it was a discussion that generated no light and a great deal of heat then. This discussion is headed in the same direction. -- Alex
[toc] | [prev] | [next] | [standalone]
| From | "HAA" <someone@microsoft.com> |
|---|---|
| Date | 2017-06-05 19:21 +1000 |
| Message-ID | <oh37ph$h2d$1@gioia.aioe.org> |
| In reply to | #60277 |
Alex wrote: > On 6/3/2017 05:29, HAA wrote: > >> And, as it stands, > >> neither you nor s/he have shown how it's possible to write such a word > >> in a standard way. > > It's not my job to make things standard. That's the role of TC's. > > To resolve the ambiguity, I'll rephrase it as "write such a word with > standard words". You haven't explained why that's important to you. Anyone who can implement EXIT, can implement UNNEST as it is a factor of EXIT. > I'm not adding any more to the discussion; > ... You can't think of an intelligent way of using CATCH THROW in the examples I posted? I'm not surprised. CATCH THROW is an exception handler of last resort, whereas UNNEST serves to alter program flow under full control of the programmer.
[toc] | [prev] | [next] | [standalone]
| From | "HAA" <someone@microsoft.com> |
|---|---|
| Date | 2017-06-03 14:19 +1000 |
| Message-ID | <ogtdsl$n0r$1@gioia.aioe.org> |
| In reply to | #60179 |
Alex wrote: > On 6/2/2017 04:09, HAA wrote: > > Andrew Haley wrote: > > ... > >> And note that we now have THROW. > > > > I've already commented on the improbability of replacing UNLOOP with THROW. > > What makes you think substituting UNNEST with THROW would be any less > > foolish? > > You're proposing UNNEST instead of THROW; it's not us proposing THROW > instead of UNNEST. I've never said THROW can be replaced by UNNEST. What I have done is counter the claims of critics proposing UNNEST can be replaced by THROW, saying that would be as ludicrous as replacing UNLOOP with THROW.
[toc] | [prev] | [next] | [standalone]
| From | Andrew Haley <andrew29@littlepinkcloud.invalid> |
|---|---|
| Date | 2017-06-02 03:32 -0500 |
| Message-ID | <xuqdnYhZU-ccv6zEnZ2dnUU7-XvNnZ2d@supernews.com> |
| In reply to | #60178 |
HAA <someone@microsoft.com> wrote: > Andrew Haley wrote: >> HAA <someone@microsoft.com> wrote: >> > Andrew Haley wrote: >> >> HAA <someone@microsoft.com> wrote: >> >> > Alex wrote: >> >> >> ... >> >> >> HAA's code won't work on any system that doesn't maintain the return >> >> >> address on the stack; for instance those that do tail-call elimination >> >> >> or inlining. I don't need to write any code to demonstrate that. >> >> > >> >> >> >> > In fact ANS does require systems to maintain "nest-sys" on the >> >> > return stack. >> >> >> >> "nest-sys" is zero to n cells in size. >> > >> > "nest-sys" is "implementation defined". What's not in doubt is that >> > nest-sys exists and it occurs whenever a subroutine is invoked. >> >> There is every reason to doubt that it exists in concrete: it is a >> conceptual structure. > > You're saying ANS and all the previous standards invented a fiction? Pretty much, yes. > That the 'return stack' in Forth has never been used to hold information > necessary for subroutine to return to its caller? Wonders never cease. No, I did not say that. >> A physical return stack that contains addresses might be somewhere >> else, or the compiler might have rewritten all of your code so that >> there are no calls. The "as if" rule applies. > > The only rule I see is the one specified by colon which says a call to a > subroutine leaves a nest-sys on the return stack. Any implementer > which seeks to avoid it is on their own. They are, but they are also compliant. The "as if" rule says this: if no strictly-conforming Standard Forth program can tell the difference, an optimization is allowed. >> >> Well, there is: no sane TC would ever agree to it. >> > >> > 'No sane TC would ever agree to' an opportunity to simplify and reduce >> > code as suggested by Forth's creator? How unfortunate for Forth. >> > >> > Charles Moore: >> > >> > "More and more I've come to favor R> DROP to alter the flow of control. >> > [...] The alternative is burdening the rest of the application with checking >> > whether an error occurred. That's an inconvenience." >> >> Quelle tragedie. > > In other words you don't have a technical reason for rejecting UNNEST. No exactly: I was mocking your attempt at using the fallacious argument from authority. The technical reasons have already been covered; what would be the purpose of repeating them? Andrew.
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2017-06-02 06:50 -0700 |
| Message-ID | <1cdad3d1-6417-4c74-b029-0975ab831fee@googlegroups.com> |
| In reply to | #60178 |
On Thursday, June 1, 2017 at 8:09:46 PM UTC-7, HAA wrote: > Andrew Haley wrote: > > There is every reason to doubt that it exists in concrete: it is a > > conceptual structure. > > You're saying ANS and all the previous standards invented a fiction? > That the 'return stack' in Forth has never been used to hold information > necessary for a subroutine to return to its caller? Wonders never cease. > > > A physical return stack that contains addresses > > might be somewhere else, or the compiler might have rewritten all of > > your code so that there are no calls. The "as if" rule applies. > > The only rule I see is the one specified by colon which says a call to a > subroutine leaves a nest-sys on the return stack. Any implementer > which seeks to avoid it is on their own. > ... > In other words you don't have a technical reason for rejecting UNNEST. > > > And note that we now have THROW. > > I've already commented on the improbability of replacing UNLOOP with THROW. > What makes you think substituting UNNEST with THROW would be any less > foolish? HAA is on the right track here. Using CATCH and THROW would be stupid. I think that it is a very bad idea to allow R> to access the return-address, because the return-address may not be on the same stack that R> accesses --- the AVR has a tiny stack for return-addresses and typically won't be used for >R R> etc. --- also, the ARM has its link-register that R> isn't going to access properly. A little bit of information-hiding works well though. UNNEST can be written in any system, although carnal knowledge will be needed --- this is a good example of a word that should be standardized because there is no way to write it in Forth to be portable --- another good example is my rquotation implementation that is easy to write in any Forth (I've done it in VFX and SwiftForth), but carnal knowledge is required because there is no way to write it in Forth to be portable.
[toc] | [prev] | [next] | [standalone]
| From | hum9 <obi65537@gmail.com> |
|---|---|
| Date | 2017-05-27 00:33 -0700 |
| Message-ID | <38c7b678-85d5-4d09-a837-e4ae8378ac50@googlegroups.com> |
| In reply to | #59852 |
On Friday, May 26, 2017 at 2:55:45 PM UTC+3, HAA wrote: > humptydumpty wrote: > > On Friday, May 26, 2017 at 8:03:30 AM UTC+3, obi6...@gmail.com wrote: > > > On Wednesday, May 24, 2017 at 8:46:07 AM UTC+3, HAA wrote: > > > > > > > > : rdini ( a u fid -- u a u | u ior ) > > > > 1 setfh ?dup if ( err) nip >ior unnest end tuck ; > > > > > > > > : ranrw ( a' size mode -- a' size | a' u' ) \ read/write 128 byte disk file record > > > > 33 + fcb swap bdos if ( eof or disk full) drop unnest r> then ; > > > > > > > > : fread ( a u1 -- a u2 ) > > > > begin dup while > > > > >r \ u remaining > > > > setsiz r@ umin ( siz) > > > > dup recsiz = if \ whole record > > > > over setdma 0 ranrw \ direct to adr > > > > else \ partial record > > > > hbuf setdma 0 ranrw \ to temp buffer > > > > 2dup hbuf offs + -rot cmove \ copy partial to adr > > > > then > > > > dup >r + rwp@ r@ m+ rwp! 2r> - \ update file pos & u remaining > > > > repeat ; > > > > > > > > : read-file ( a u1 fid -- u2 ior ) > > > > rdini ( u a u) fread ( u a' u') nip - 0 ; > > > > > > > > > Just my taste of that code is: > > > (I deleted my previous post because bad updating file pos & u remaining.) > > > > > > : rdini ( a u fid -- a u | u ior ) > > > 1 setfh ?dup if ( err) nip >ior unnest then ; > > > > > > : rwrec ( a size mode -- a size failure) \ read/write 128 byte disk file record > > > 33 + fcb swap bdos ; > > > > > > : +record ( u a size mode -- u a size | u) > > > rwrec if 2drop unnest then ; > > > > > > : fread ( a u -- u') > > > begin dup while > > > tuck setsiz umin ( siz) > > > dup recsiz = if \ whole record > > > over setdma 0 +record \ direct to adr > > > else \ partial record > > > hbuf setdma 0 +record \ to temp buffer > > > 2dup hbuf offs + -rot cmove \ copy partial to adr > > > then > > > dup >r + rwp@ r@ m+ rwp! swap r> - \ update file pos & u remaining > > > repeat nip ; > > > > > > : read-file ( a u1 fid -- u2 ior ) > > > rdini ( a u) tuck fread ( u') nip - 0 ; > > > > > > Have a nice day, > > > hum9 > > > > Phew! > > > > : read-file ( a u1 fid -- u2 ior ) > > rdini ( a u) tuck fread ( u') - 0 ; > > Interesting to see you tackle that :) It was a good exercise for me, a little bit of DOS nostalgia, and I think I learned something :) > The point of the example was to demonstrate > the use of unnest to gain access to a value previously placed on the return stack. > While you managed to avoid the need for it in this case, it remains a feature of > unnest. My other point was efficiency. I'd be horrified at the thought of anyone > attempting to use catch/throw in code such as this. At first time when I understood 'ranrw' and its use on 'fread' I recognized that will be very hard to write a more efficient forth code. I've seen that most time 2 items are used data stack which is a sign of good factoring and readability/understanding. Also recognized a tight cooperation data/return stack, more than in usual factoring. Thanks for pointing to that forth gem :) Have a nice day, hum9
[toc] | [prev] | [next] | [standalone]
| From | "HAA" <someone@microsoft.com> |
|---|---|
| Date | 2017-05-27 14:53 +1000 |
| Message-ID | <ogb0o0$11al$1@gioia.aioe.org> |
| In reply to | #59844 |
obi65537@gmail.com wrote:
> On Friday, May 26, 2017 at 8:03:30 AM UTC+3, obi6...@gmail.com wrote:
> > ...
> > Just my taste of that code is:
> > (I deleted my previous post because bad updating file pos & u remaining.)
> >
> > : rdini ( a u fid -- a u | u ior )
> > 1 setfh ?dup if ( err) nip >ior unnest then ;
> > ...
>
> Phew!
>
> : read-file ( a u1 fid -- u2 ior )
> rdini ( a u) tuck fread ( u') - 0 ;
Like the move of tuck from rdini to just before fread. It's logically better
and simplifies the code a little.
I discover u2 is supposed to be meaningful when ior <> 0, so
: rdini ( a u fid -- a u | 0 ior )
1 setfh ?dup if ( err) 0 swap 2nip >ior unnest then ;
[toc] | [prev] | [next] | [standalone]
Page 8 of 11 — ← Prev page 1 … 6 7 [8] 9 10 11 Next page →
Back to top | Article view | comp.lang.forth
csiph-web