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 6 of 11 — ← Prev page 1 … 4 5 [6] 7 8 … 11 Next page →
| From | Alex <alex@rivadpm.com> |
|---|---|
| Date | 2017-06-02 14:30 +0100 |
| Message-ID | <ogrp3r$sqa$1@dont-email.me> |
| In reply to | #60191 |
On 6/2/2017 14:16, Albert van der Horst wrote: > In article <RqidndL6EYGy_6zEnZ2dnUU7-fudnZ2d@supernews.com>, > Andrew Haley <andrew29@littlepinkcloud.invalid> wrote: >> Alex <alex@rivadpm.com> wrote: >>> On 6/1/2017 21:48, hughaguilar96@gmail.com wrote: >>>> Now, here is the Forth-200x committee chairman desperately trying to >>>> add infix notation to Forth. >>> >>> Don't be such an enormous cockwomble. Of course he's not. >> >> Yay! The first use of "cockwomble" on c.l.f., as far as I can >> remember. Something to celebrate. :-) <bows> > > Is there more to know than that it is a peiorative? > Not really. https://notesfromtheuk.com/tag/cockwombles/ -- Alex
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2017-06-02 07:32 -0700 |
| Message-ID | <c4423f85-dda9-4318-bbd6-6cceed7b3254@googlegroups.com> |
| In reply to | #60192 |
On Friday, June 2, 2017 at 6:30:56 AM UTC-7, Alex wrote:
> On 6/2/2017 14:16, Albert van der Horst wrote:
> > In article <RqidndL6EYGy_6zEnZ2dnUU7-fudnZ2d@supernews.com>,
> > Andrew Haley <andrew29@littlepinkcloud.invalid> wrote:
> >> Alex <alex@rivadpm.com> wrote:
> >>> On 6/1/2017 21:48, hughaguilar96@gmail.com wrote:
> >>>> Now, here is the Forth-200x committee chairman desperately trying to
> >>>> add infix notation to Forth.
> >>>
> >>> Don't be such an enormous cockwomble. Of course he's not.
> >>
> >> Yay! The first use of "cockwomble" on c.l.f., as far as I can
> >> remember. Something to celebrate. :-)
>
> <bows>
ANS-Forth is a cult. Elizabeth Rather has surrounded herself with twits and creeps. To be an ANS-Forth programmer, a person must be filthy, nasty and vulgar --- if you don't believe me, then ask Andrew Haley --- Andrew Haley is such a filthy, nasty and vulgar twit that Elizabeth Rather appointed him to the Forth-200x committee!
ANS-Forth programmers are also liars. Alex McDonald says that "of course" Anton Ertl isn't trying to add infix notation to Forth. This is the discussion he is referencing:
On Thursday, June 1, 2017 at 1:48:16 PM UTC-7, hughag...@gmail.com wrote:
> On Wednesday, May 31, 2017 at 10:49:54 PM UTC-7, Anton Ertl wrote:
> > The power you can exert at a recognizer is the full power of Forth.
> > You can have a recognizer that recognizer A^nB^nC^n; try that with a
> > recursive-descent parser.
> > ...
>
> The reason why Algol and its many derivatives don't allow A^nB^nC^n is because their variables names can have more than one letter in them, so they can't use juxtaposition to represent multiplication. If you define a symbol as being one-letter though, then it is trivial to write a recursive-descent parser to accept: A^nB^nC^n
Here is yet another lie from Alex McDonald:
> > Is there more to know than that [cockwomble] is a peiorative?
>
> Not really.
I never heard the term before Alex McDonald use it here on comp.lang.forth, so I looked it up in Urban Dictionary:
"The literal meaning of cockwomble is someone who engages in cottaging or gay dogging type activities in public places."
I don't actually know what "cottaging or gay dogging" mean, although I expect that Alex McDonald does --- something to do with homosexuality.
Alex McDonald knows that I am not tolerant of homosexuality being promoted on comp.lang.forth --- because I complained about John Passaniti routinely promoting homosexuality on comp.lang.forth --- John Passaniti had 100% support from Elizabeth Rather, Stephen Pelc and Bernd Paysan in this regard however (this was *after* John Passaniti openly talked about group gay sex and masturbation on comp.lang.forth).
Alex McDonald hopes that he can get an emotional response out of me by calling me a homosexual on comp.lang.forth --- and he knows that he can continue to enjoy 100% support from Elizabeth Rather, Stephen Pelc and Bernd Paysan --- Alex McDonald is trying to get himself appointed to the Forth-200x committee, following in the footsteps of Andrew Haley, and I predict that either Alex McDonald or Julien Fondren or both will be appointed to the Forth-200x committee soon, because they are fully the equal of Andrew Haley in their filth, and filth is what Elizabeth Rather wants!
Albert van der Horst is also trying to get appointed to the Forth-200x committee. Here is an example of him trying to impress Elizabeth Rather with his loyalty:
https://groups.google.com/forum/#!searchin/comp.lang.forth/lc53%7Csort:relevance/comp.lang.forth/qqlp1gZnVic/kjeAwWCaR1MJ
This was one of Albert van der Horst's many lies in that thread:
On Monday, November 25, 2013 at 12:32:44 PM UTC-7, Albert van der Horst wrote:
> Hugh suggests that the only difference with his LC53 is that
> Anton Ertl and Elizabeth Rather inspire more confidence than he does.
>
> It sounds like you have a whole machinery in place to tests rng's.
> Would you mind adding LC53 to the list?
>
> \ Comma for clarity, not a double number.
> : LC53 -5 um* -333,333,333 + nip ;
> ( : doit seed @ LC53 dup seed ! ; )
He is posting non-working code and claiming that I wrote it, but that is not my code --- he is just lying --- this is my code:
4294967291 constant rnd-unity \ 2^32 - 5
3961633963 constant rnd-mult \ 2^32 - 333333333
macro: <prng> ( rnd -- new-rnd )
rnd-mult um* rnd-unity um/mod drop ;
[toc] | [prev] | [next] | [standalone]
| From | Alex <alex@rivadpm.com> |
|---|---|
| Date | 2017-06-02 18:23 +0100 |
| Message-ID | <ogs6oc$eom$1@dont-email.me> |
| In reply to | #60197 |
On 6/2/2017 15:32, hughaguilar96@gmail.com wrote: > I never heard the term before Alex McDonald use it here on > comp.lang.forth, so I looked it up in Urban Dictionary: "The literal > meaning of cockwomble is someone who engages in cottaging or gay > dogging type activities in public places." No, that's made up, like most of the urban dictionary. > > I don't actually know what "cottaging or gay dogging" mean, although > I expect that Alex McDonald does --- something to do with > homosexuality. > > Alex McDonald knows that I am not tolerant of homosexuality being > promoted on comp.lang.forth --- because I complained about John > Passaniti routinely promoting homosexuality on comp.lang.forth --- > John Passaniti had 100% support from Elizabeth Rather, Stephen Pelc > and Bernd Paysan in this regard however (this was*after* John > Passaniti openly talked about group gay sex and masturbation on > comp.lang.forth). > > Alex McDonald hopes that he can get an emotional response out of me > by calling me a homosexual on comp.lang.forth I think you're having a "Ted Haggard" moment. -- Alex
[toc] | [prev] | [next] | [standalone]
| From | Julian Fondren <julian.fondren@gmail.com> |
|---|---|
| Date | 2017-06-01 14:49 -0700 |
| Message-ID | <0706edfb-16e8-4675-ac36-432eaa3036a3@googlegroups.com> |
| In reply to | #60164 |
On Thursday, June 1, 2017 at 3:48:16 PM UTC-5, hughag...@gmail.com wrote: > Now, here is the Forth-200x committee chairman desperately trying to add infix notation to Forth. Forth has that: https://www.taygeta.com/fsl/docs/551.jvn.fall01/ftrandoc.txt Recognizers can add operator-like syntax (a::b to mean B in the A wordlist; ->b to mean TO B; a.b to mean A >O B O>), and they do completely weird things (any line of code that doesn't start with two spaces is a comment; a word in all caps is looked up in the FORTH wordlist regardless of order), and they can also add literals for arbitrary data structures, like (1,2,3) compiled to the string literal: s\" \x03\x00\x00\x00\x01\x00\x00\x00\x02\x00\x00\x00\x03\x00\x00\x00" Recognizers aren't "inflix notation for Forth". Since any word can take over compilation, you can already do all of this in Forth. What recognizers add is the ability to *only* say "I want words in all caps to be treated specially" and see that done -- without reimplementing the entire 'outer interpreter', and with easy interoperability with other recognizers. You could release a library that changes double literals so that they get pushed to their own stack, and people could write code in this variant of Forth while still using (not without some double-passing trouble) other libraries written in ANS Forth or using other recognizers. Recognizers can convert a lot of useless how-Forth-should-be advocacy into code that people can then use or not use. > This makes Forth appear to be stupid and meaningless --- Forth appears to be a clumsy effort to write a C compiler --- I really recommend that Anton Ertl stick with C programming and stop pretending to be a Forth programmer! "Other people's opinions according to <some guy>" is more impressive when the Some guy doesn't constantly ascribe insane opinions and motivations to other people.
[toc] | [prev] | [next] | [standalone]
| From | minforth@arcor.de |
|---|---|
| Date | 2017-06-01 16:05 -0700 |
| Message-ID | <4f657bda-38b5-45ba-9bb0-511e3285eec4@googlegroups.com> |
| In reply to | #60168 |
Am Donnerstag, 1. Juni 2017 23:49:16 UTC+2 schrieb Julian Fondren: > Since any word can take over compilation, you can already do all of > this in Forth. What recognizers add is the ability to *only* say "I > want words in all caps to be treated specially" and see that done -- > without reimplementing the entire 'outer interpreter', and with easy > interoperability with other recognizers. You could release a library > that changes double literals so that they get pushed to their own > stack, and people could write code in this variant of Forth while > still using (not without some double-passing trouble) other libraries > written in ANS Forth or using other recognizers. Thanks. This is the most sensible storyline for recognizers that I met so far. Forth is a strong tool for creating your application-specific "wordset" or DSL if you like, and application-specific data formats come along with it. Although I find the current proposal and discussion exaggerated and I haven't needed fancy name tokens in decades, and although I find it strange to talk about libraries when each Forth system sticks to its own legacy dialect, recognizers might help to invent even more dialects. ;-)
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2017-06-01 17:48 -0700 |
| Message-ID | <c72a5348-0c01-4704-8e6b-f93ec8e9772e@googlegroups.com> |
| In reply to | #60168 |
On Thursday, June 1, 2017 at 2:49:16 PM UTC-7, Julian Fondren wrote: > Recognizers can add operator-like syntax (a::b to mean B in the A > wordlist; ->b to mean TO B; a.b to mean A >O B O>), and they do > completely weird things (any line of code that doesn't start with two > spaces is a comment; a word in all caps is looked up in the FORTH > wordlist regardless of order), and they can also add literals for > arbitrary data structures, like (1,2,3) compiled to the string > literal: > s\" \x03\x00\x00\x00\x01\x00\x00\x00\x02\x00\x00\x00\x03\x00\x00\x00" > > Recognizers aren't "inflix notation for Forth". > > Since any word can take over compilation, you can already do all of > this in Forth. What recognizers add is the ability to *only* say "I > want words in all caps to be treated specially" and see that done -- > without reimplementing the entire 'outer interpreter', and with easy > interoperability with other recognizers. You could release a library > that changes double literals so that they get pushed to their own > stack, and people could write code in this variant of Forth while > still using (not without some double-passing trouble) other libraries > written in ANS Forth or using other recognizers. Every program will have a dependency on having certain recognizers installed, and these recognizers installed in a certain order because they likely clash with each other --- code will not run on a Forth-200x system unless it is configured in exactly the correct way --- but configuring the Forth-200x system in one way will break all of the code that requires it to be configured in another way. If your program assumes that words with all capital letters mean something different than usual, what will happen to code that contains words with all capital letters just because the programmer felt like doing that, but did so prior to you writing your funky recognizer that imposes your own meaning on this? That code will be broken! Recognizers will totally kill the possibility of code-libraries that are portable between standard Forth systems --- Forth-200x is actually worse than ANS-Forth --- in ANS-Forth my novice-package works under any ANS-Forth system, and I don't have to specify a dependency on a certain configuration of recognizers. I said before that LITERAL 2LITERAL and FLITERAL need to be vectorized for use in a cross-compiler --- this doesn't mean that I want willy-nilly redefinitions of these words in ordinary application programs --- incompatibilities and dependencies need to have some purpose, but recognizers seem to only have the purpose of allowing artistic types to define their own funky syntax that is different from everybody else's. I would expect most recognizers to be written late at night on the encouragement of Jose Cuervo --- this would be done by programmers trying to create a "meme" that goes viral throughout the Forth world because it is "kewl" --- this will destroy any credibility that Forth ever had as a professional programming-language. Doing "completely weird things" is not the best way to convince the real-world to take Forth seriously.
[toc] | [prev] | [next] | [standalone]
| From | Julian Fondren <julian.fondren@gmail.com> |
|---|---|
| Date | 2017-06-01 18:44 -0700 |
| Message-ID | <579506c3-ccef-4f30-b5a8-1f514af3d858@googlegroups.com> |
| In reply to | #60170 |
On Thursday, June 1, 2017 at 7:48:36 PM UTC-5, hughag...@gmail.com wrote: > > Every program will have a dependency on having certain recognizers installed, and these recognizers installed in a certain order because they likely clash with each other --- code will not run on a Forth-200x system unless it is configured in exactly the correct way --- but configuring the Forth-200x system in one way will break all of the code that requires it to be configured in another way. > The solution to this is a word that gives the recognizer stack a definite configuration. You invoke it and then supply the code that assumes it. In the absence of such a word you have an assumed syntax, like you have an assumed BASE. You'd get his solution anyway because, like ALSO ALSO ALSO PREVIOUS DEFINITIONS , the recognizer stack is a tedious thing to deal with every time you want to deal with it. Just start your programs with +LITERATE +DOUBLE-STACK For ANS Forth except some modifications, or RETROFORTH For Retro's syntax (and vocabulary in the search order), etc. > If your program assumes that words with all capital letters mean something different than usual, what will happen to code that contains words with all capital letters just because the programmer felt like doing that, but did so prior to you writing your funky recognizer that imposes your own meaning on this? That code will be broken! If your program assumes the definitions of certain words, what will happen to code that assumes *other* definitions of words?! This is a problem we already have. It's not a big deal and won't be. It's solved by *documentation*, a thing that is not even code, it's so easy to write. > > Recognizers will totally kill the possibility of code-libraries that > are portable between standard Forth systems [cats and dogs living > together, cross compilers, kids these days] > Kids these days can already do such things. They can do them on those Forths that support recognizers, and they can do them with their own parsing words, and they can do them by rolling their own Forths with their own innovative syntaxes. The results in all cases are pretty benign, except that it's harder to port the resulting code to a Forth without recognizers. ciforth isn't filled with gimmicks; it just has "strings" like most programmers are comfortable with. gforth likewise has obj.method invocation (in mini-oof2.fs) like most programmers are comfortable with. The variant Forths that people write generally have good ideas like JSON literals and at least arguable ideas like quotation-heavy code. Of portability, Forths already have small bits of divergent syntax. SwiftForth has relatively permissive double literals for example. So recognizers are a solution to the existing problems, not just a source of new potential problems (fixable by wider recognizer support). I think it's worth worrying about silly-balls extensions. I think "worrying about it" is also completely sufficient action. Now that you've worried, and made your worries public, you've done your job, you can move on. Perl also has this, that loaded modules can change the syntax of the language. This annoys me when doing development on multiple machines because you can't even do a 'perl -c' syntax check without being able to load every module a script is using, because those modules *might* change the language. The results for Perl? Well there are some joke modules that load source consisting of whitespace characters only into a Perl program, and there are some tasteful uses of the feature, like in modules that make OO programming nicer in Perl. Just "use Spiffy -Base;" and then your class methods no longer have to explicitly accept $self as a parameter: http://search.cpan.org/~ingy/Spiffy-0.46/lib/Spiffy.pod For the most part it goes unused -- but, Perl is lower-level and a more primitive language than Forth, doesn't even have a standard, so naturally this feature isn't as capable or as reliable as recognizers.
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2017-06-01 19:14 -0700 |
| Message-ID | <59542db8-54b8-426c-b24e-488728617b5d@googlegroups.com> |
| In reply to | #60174 |
This is what Julien Fondren said earlier today: On Thursday, June 1, 2017 at 2:49:16 PM UTC-7, Julian Fondren wrote: > Recognizers can ... do > completely weird things... This is what Julien Fondren says now: On Thursday, June 1, 2017 at 6:44:44 PM UTC-7, Julian Fondren wrote: > I think it's worth worrying about silly-balls extensions. I think > "worrying about it" is also completely sufficient action. Now that > you've worried, and made your worries public, you've done your job, > you can move on. He is telling me to get out of the way and let him have his fun --- for him, Forth-200x is the programming world's version of the Burning Man Festival --- everybody gets to do their own thing without any criticism (and also without having a point). Making recognizers part of the Forth-200x "Standard" will destroy the credibility of Forth --- the only people interested will be self-proclaimed "creatives" who dream about inventing a "meme" that goes viral around the world because it is "kewl" --- John Passaniti or Julien Fondren would be obvious examples of this type of "programmer."
[toc] | [prev] | [next] | [standalone]
| From | Julian Fondren <julian.fondren@gmail.com> |
|---|---|
| Date | 2017-06-01 19:54 -0700 |
| Message-ID | <607ae318-4ac4-4c75-8666-c171a4164d10@googlegroups.com> |
| In reply to | #60175 |
On Thursday, June 1, 2017 at 9:14:14 PM UTC-5, hughag...@gmail.com wrote:
> This is what Julien Fondren said earlier today:
Looks like you're no longer lucid. I'll reply accordingly.
>
> He is telling me to get out of the way and let him have his fun
: rotated-forth ( -- )
begin refill while
source 2dup bounds ?do i c@
dup bl or
dup [char] a [ char m 1+ ] literal within if drop 13 + i c! else
[char] n [ char z 1+ ] literal within if 13 - i c! else
drop then then
loop evaluate
repeat ;
ROTATED-FORTH
pe .( Gung'f evtug.)
pe .( Naq gurer'f abguvat lbh pna qb gb fgbc zr!)
pe .( OJNUNUNUNUN)
olr
That's limited though.
... files were a mistake.
[toc] | [prev] | [next] | [standalone]
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2017-05-27 17:40 +0000 |
| Message-ID | <2017May27.194018@mips.complang.tuwien.ac.at> |
| In reply to | #59880 |
anton@mips.complang.tuwien.ac.at (Anton Ertl) writes:
>: bench-catch
> 100000000 0 ?do ['] noop catch throw loop ;
>
>: ESC ( rp -- ) RP! ;
>: ESCAPES> ( xt[rp--] -- ) RP@ swap EXECUTE ;
>
>: escaping-word1 ( .. rp -- ... ) true IF drop fdrop ESC THEN ;
>: working-word1 ( .. rp -- ... ) 1 1e escaping-word1 drop fdrop ;
>: current-word1 ( .. -- ... ) ['] working-word1 ESCAPES> ;
>
>: escaping-word2 ( .. -- ... ) true if 1 fast-throw then ;
>: working-word2 ( .. -- ... ) 1 1e escaping-word2 drop fdrop ;
>: current-word2 ( .. -- ... ) ['] working-word2 CATCH drop ;
>
>: bench-esc
> 100000000 0 ?do current-word1 loop ;
>
>: bench-fthrow
> 100000000 0 ?do current-word2 loop ;
>
>FAST-THROW is a THROW that does not produce a backtrace and always
>throws (that's why it is wrapped in IF..THEN here).
>
>Results in cycles per iteration on Gforth-fast (development version):
>31 bench-esc
>95 bench-fthrow
>73 bench-catch
(Hardware: Core i5-6600K)
>So we could improve the performance of BENCH-FTHROW by improving the
>performance of CATCH (which is possible). But even so, 95 cycles is
>not that expensive.
I cleaned up and streamlined the CATCH and THROW implementation
(commits c7ec559..d0efb1b), and now these benchmarks give the
following results:
33 bench-esc
41 bench-throw
28 bench-catch
I don't know why bench-esc is now slower by 2 cycles per iteration; my
guess is that it now does not sit as well aligned in the I-cache as
before (the earlier result had 4.01 IPC, which is extremely high).
Anyway, at least the FAST-THROW variant is competetive with the
ESC/ESCAPES> variant, and it also works for programs with locals.
THROW is more heavyweight in Gforth, mainly because it also stores a
backtrace. Defining
: escaping-word2 1 throw ;
increases the cost per iteration to 154 cycles.
One could also do a variant of CATCH that catches only one kind of
ball; that would be a better fit for this kind of usage than the
general CATCH. But I'll look into that on another day.
- 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 | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2017-05-30 15:28 +0000 |
| Subject | WRAP...END-WRAP (was: Would ?EXIT work ...) |
| Message-ID | <2017May30.172812@mips.complang.tuwien.ac.at> |
| In reply to | #59934 |
For some time we have discussed using CATCH and THROW for multi-level
exits in non-exceptional situations. They have several advantages
(especially compared to return-address manipulations), but the "ball"
seems to be overkill and having to handle it is a nuisance.
So I experimentally designed a variant of CATCH/THROW for the problem
at hand:
wrap code1 end-wrap
executes code1; code1 can contain EXIT-WRAP, which resets the stacks
to their depth at WRAP, and then jumps behind the next enclosing
END-WRAP. No ball involved. Let's see how that basic design
performs, and how it compares to CATCH/FAST-THROW and to
return-address manipulation.
anton@mips.complang.tuwien.ac.at (Anton Ertl) writes:
>anton@mips.complang.tuwien.ac.at (Anton Ertl) writes:
>>: bench-catch
>> 100000000 0 ?do ['] noop catch throw loop ;
>>
>>: ESC ( rp -- ) RP! ;
>>: ESCAPES> ( xt[rp--] -- ) RP@ swap EXECUTE ;
>>
>>: escaping-word1 ( .. rp -- ... ) true IF drop fdrop ESC THEN ;
>>: working-word1 ( .. rp -- ... ) 1 1e escaping-word1 drop fdrop ;
>>: current-word1 ( .. -- ... ) ['] working-word1 ESCAPES> ;
>>
>>: escaping-word2 ( .. -- ... ) true if 1 fast-throw then ;
>>: working-word2 ( .. -- ... ) 1 1e escaping-word2 drop fdrop ;
>>: current-word2 ( .. -- ... ) ['] working-word2 CATCH drop ;
>>
>>: bench-esc
>> 100000000 0 ?do current-word1 loop ;
>>
>>: bench-fthrow
>> 100000000 0 ?do current-word2 loop ;
To this I add:
: bench-escapes>
100000000 0 ?do ['] noop escapes> drop loop ;
: bench-wrap
100000000 0 ?do wrap end-wrap loop ;
: escaping-word3 ( .. -- ... ) true if exit-wrap then ;
: working-word3 ( .. -- ... ) 1 1e escaping-word3 drop fdrop ;
: current-word3 ( .. -- ... ) wrap working-word3 end-wrap ;
: bench-exit-wrap
100000000 0 ?do current-word3 loop ;
CATCH and ESCAPES> force you to pass the wrapped code as xt, but we
have no such restriction with WRAP...END-WRAP, and in the following,
we make use of that.
: current-word4 ( .. -- ... ) wrap 1 1e escaping-word3 drop fdrop end-wrap ;
: bench-exit-wrap-inline
100000000 0 ?do current-word4 loop ;
Also, current-word2 does not deal with the ball properly, so let's
have a proper version of that:
: current-word5 ( .. -- ... ) ['] working-word2 CATCH dup 1 <> and throw ;
: bench-fthrow2
100000000 0 ?do current-word2 loop ;
Results in cycles per iteration on gforth-fast (development version)
on a Core i5-6600K:
First, let's see what the wrapping itself costs:
28 bench-catch
11 bench-wrap
13 bench-escapes>
And the current-working-escaping sequence:
41 bench-fthrow
53 bench-fthrow2
33 bench-exit-wrap
33 bench-exit-wrap-inline (but 10 instructions/iteration less)
31 bench-esc
So WRAP...END-WRAP/EXIT-WRAP provides a small run-time advantage over
CATCH/FAST-THROW, probably not enough to justify adding a new
mechanism.
Is the easier programming enough to justify the new mechanism?
Alternatively, we can define:
1 constant wrap-exception
: exit-wrap wrap-exception throw ;
: wrap-exec ( xt -- )
catch dup wrap-exception <> and throw ;
So WRAP..END-WRAP/EXIT-WRAP does not make programming significantly
simpler compared to a CATCH/THROW-based solution, either. Maybe you
still find this feature useful enough that we should keep it in Gforth
(it's currently in the git as experimental extension); if you do,
please let me know, otherwise I am going to remove it soon.
If we keep it, do we need anything else to make it more practical? In
wrap code1 end-wrap
CODE1 needs to have the stack effect ( -- ). If we want to remove
this restriction, we need to have a separate piece of code for the
EXIT-WRAP case:
wrap code1 wrap-onexit code2 then
Here CODE2 is only executed if CODE1 is left through EXIT-WRAP; this
feature is currently implemented in Gforth.
If we want EXIT-WRAP to be able to return some values to the wrapper,
we would need to e.g., tell a variant of EXIT-WRAP how many cells and
FP items we want to return (all EXIT-WRAPs for the same wrapper need
to return the same number). E.g., have a word
xf-exit-wrap ( ui*x uj*r ui uj -- )
and the ui*x uj*r are pushed on the stacks after restoring the stack
depths.
If we pass values into WRAP...END-WRAP on the stacks that is not
needed later, it could be more convenient if the restoring of the
stack depth by EXIT-WRAP dropped these values automatically. For that
we would need something like
xf-wrap ( ui*x uj*r ui uj -- ui*x uj*r )
and EXIT-WRAP would restore the stack depths to the depth without ui*x
uj*r.
The XF-... ideas are not implemented in Gforth.
- 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 | "HAA" <someone@microsoft.com> |
|---|---|
| Date | 2017-05-24 15:46 +1000 |
| Message-ID | <og36ma$1883$1@gioia.aioe.org> |
| In reply to | #59352 |
humptydumpty wrote:
> On Tuesday, May 16, 2017 at 3:24:34 AM UTC+3, HAA wrote:
> > Lars Brinkhoff wrote:
> > > HAA wrote:
> > > > It expresses a functionality which at the time was implemented through
> > > > R> DROP. For all I know ANS TC simply forgot to consider this use in its
> > > > R> deliberations.
> > >
> > > Isn't it the case that the 1994 ANS explicitly spells out that return
> > > addresses may not be accessible at all by R>?
> >
> > Exactly. So if you want to drop a level in ANS you'll need another
> > mechanism to do it. I chose to implement a word called UNNEST,
> > the definition of which will vary from system to system.
>
> One of quick & dirty multilevel drop that I thought is pair:
>
> : ESC ( rp -- ) RP! ;
> : ESCAPES> ( xt[rp--] -- ) RP@ swap EXECUTE ;
>
> And used something like:
>
> : escaping-word ( .. rp -- ... ) .. IF ESC THEN ... ;
> : working-word ( .. rp -- ... ) .. escaping-word ... ;
> : current-word ( .. -- ... ) ['] working-word ESCAPES> ... ;
>
> Another one, more flexible, but same principle is at:
> http://theforth.net/package/callec
Looking at the example above and first example in callec, I'd still go with
r> drop (aka unnest) because they don't require anything complex e.g.
: escaping-word ( ... -- ... ) .. IF unnest THEN ... ;
: working-word ( ... -- ... ) .. escaping-word ... ;
: current-word ( ... -- ... ) working-word ... ;
The challenge for Callec will be finding uses for which neither CATCH THROW
nor UNNEST is suitable. For example unnest lets you do things catch/throw
was never designed to do.
: 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 ;
[toc] | [prev] | [next] | [standalone]
| From | humptydumpty <obi65537@gmail.com> |
|---|---|
| Date | 2017-05-25 11:51 -0700 |
| Message-ID | <43f898d2-f648-4d49-ae94-d64f767cf314@googlegroups.com> |
| In reply to | #59765 |
On Wednesday, May 24, 2017 at 8:46:07 AM UTC+3, HAA wrote: > humptydumpty wrote: > > On Tuesday, May 16, 2017 at 3:24:34 AM UTC+3, HAA wrote: > > > Lars Brinkhoff wrote: > > > > HAA wrote: > > > > > It expresses a functionality which at the time was implemented through > > > > > R> DROP. For all I know ANS TC simply forgot to consider this use in its > > > > > R> deliberations. > > > > > > > > Isn't it the case that the 1994 ANS explicitly spells out that return > > > > addresses may not be accessible at all by R>? > > > > > > Exactly. So if you want to drop a level in ANS you'll need another > > > mechanism to do it. I chose to implement a word called UNNEST, > > > the definition of which will vary from system to system. > > > > One of quick & dirty multilevel drop that I thought is pair: > > > > : ESC ( rp -- ) RP! ; > > : ESCAPES> ( xt[rp--] -- ) RP@ swap EXECUTE ; > > > > And used something like: > > > > : escaping-word ( .. rp -- ... ) .. IF ESC THEN ... ; > > : working-word ( .. rp -- ... ) .. escaping-word ... ; > > : current-word ( .. -- ... ) ['] working-word ESCAPES> ... ; > > > > Another one, more flexible, but same principle is at: > > http://theforth.net/package/callec > > Looking at the example above and first example in callec, I'd still go with > r> drop (aka unnest) because they don't require anything complex e.g. > > : escaping-word ( ... -- ... ) .. IF unnest THEN ... ; > : working-word ( ... -- ... ) .. escaping-word ... ; > : current-word ( ... -- ... ) working-word ... ; > > The challenge for Callec will be finding uses for which neither CATCH THROW > nor UNNEST is suitable. If have to drop more than one level and there is a single point of continuation I prefer callec , as it brings easy testing (and relative light-weight) advantages. Also is high-limited by how many levels I have to pass an xt on TOS. Depending on context one could store that xt in a variable, etc. > For example unnest lets you do things catch/throw > was never designed to do. > > : 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 ; Fine way of parameter passing! ;) I'll have to think if there is another way to put that functionality in less words. :) Have a nice day, hum9
[toc] | [prev] | [next] | [standalone]
| From | humptydumpty <obi65537@gmail.com> |
|---|---|
| Date | 2017-05-25 20:38 -0700 |
| Message-ID | <fb3bf88e-4e0b-4935-82b9-dc98479ed5c9@googlegroups.com> |
| In reply to | #59765 |
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 ;
I would not say this version is better, just is my taste:
: 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 u1 -- u2 )
tuck
begin dup while
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
tuck + rwp@ fourth m+ rwp! - \ update file pos & u remaining
repeat nip - ;
: read-file ( a u1 fid -- u2 ior )
rdini ( a u) fread ( u') 0 ;
Have a nice day,
hum9
[toc] | [prev] | [next] | [standalone]
| From | obi65537@gmail.com |
|---|---|
| Date | 2017-05-25 22:03 -0700 |
| Message-ID | <4a8821d2-4420-4cea-9e0d-a4cb337a9e57@googlegroups.com> |
| In reply to | #59765 |
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
[toc] | [prev] | [next] | [standalone]
| From | obi65537@gmail.com |
|---|---|
| Date | 2017-05-25 22:09 -0700 |
| Message-ID | <16ec2ad7-a7e9-411d-acba-e29b6ca51e21@googlegroups.com> |
| In reply to | #59843 |
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 ;
[toc] | [prev] | [next] | [standalone]
| From | "HAA" <someone@microsoft.com> |
|---|---|
| Date | 2017-05-26 21:56 +1000 |
| Message-ID | <og953t$cpo$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: > > 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 :) 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.
[toc] | [prev] | [next] | [standalone]
| From | Alex <alex@rivadpm.com> |
|---|---|
| Date | 2017-05-26 13:30 +0100 |
| Message-ID | <og96ur$789$2@dont-email.me> |
| In reply to | #59852 |
On 5/26/2017 12:56, HAA wrote: > My other point was efficiency. I'd be horrified at the thought of > anyone attempting to use catch/throw in code such as this. > Why? -- Alex
[toc] | [prev] | [next] | [standalone]
| From | "HAA" <someone@microsoft.com> |
|---|---|
| Date | 2017-05-27 15:04 +1000 |
| Message-ID | <ogb1bi$11u5$1@gioia.aioe.org> |
| In reply to | #59856 |
Alex wrote: > On 5/26/2017 12:56, HAA wrote: > > > My other point was efficiency. I'd be horrified at the thought of > > anyone attempting to use catch/throw in code such as this. > > > > Why? Forth is about using the right tool for the job?
[toc] | [prev] | [next] | [standalone]
| From | Alex <alex@rivadpm.com> |
|---|---|
| Date | 2017-05-27 17:33 +0100 |
| Message-ID | <ogc9hu$mqk$1@dont-email.me> |
| In reply to | #59892 |
On 5/27/2017 06:04, HAA wrote: > Alex wrote: >> On 5/26/2017 12:56, HAA wrote: >> >>> My other point was efficiency. I'd be horrified at the thought of >>> anyone attempting to use catch/throw in code such as this. >>> >> >> Why? > > Forth is about using the right tool for the job? > > > OK, so why is it the wrong tool for the job? Is it the names? -- Alex
[toc] | [prev] | [next] | [standalone]
Page 6 of 11 — ← Prev page 1 … 4 5 [6] 7 8 … 11 Next page →
Back to top | Article view | comp.lang.forth
csiph-web