Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #55968 > unrolled thread
| Started by | Helmar Wodtke <helmwo@gmail.com> |
|---|---|
| First post | 2017-03-20 09:58 -0700 |
| Last post | 2017-03-24 17:52 -0700 |
| Articles | 20 on this page of 212 — 28 participants |
Back to article view | Back to comp.lang.forth
Make Forth Small Again! Helmar Wodtke <helmwo@gmail.com> - 2017-03-20 09:58 -0700
Re: Make Forth Small Again! Paul Rubin <no.email@nospam.invalid> - 2017-03-20 10:34 -0700
Re: Make Forth Small Again! Helmar Wodtke <helmwo@gmail.com> - 2017-03-20 10:51 -0700
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-20 18:08 +0000
Re: Make Forth Small Again! NN <november.nihal@gmail.com> - 2017-03-20 12:19 -0700
Re: Make Forth Small Again! Helmar Wodtke <helmwo@gmail.com> - 2017-03-21 05:51 -0700
Re: Make Forth Small Again! Coos Haak <htrofhc@gmail.com> - 2017-03-21 15:04 +0100
Re: Make Forth Small Again! "Elizabeth D. Rather" <erather@forth.com> - 2017-03-21 11:22 -1000
Re: Make Forth Small Again! Helmar Wodtke <helmwo@gmail.com> - 2017-03-21 14:47 -0700
Re: Make Forth Small Again! Coos Haak <htrofhc@gmail.com> - 2017-03-22 01:34 +0100
Re: Make Forth Small Again! "HAA" <someone@microsoft.com> - 2017-03-25 17:27 +1100
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-25 00:06 -0700
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-25 01:02 -0700
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-25 01:05 -0700
Re: Make Forth Small Again! "HAA" <someone@microsoft.com> - 2017-03-27 12:11 +1000
Re: Make Forth Small Again! "HAA" <someone@microsoft.com> - 2017-03-27 15:53 +1000
Re: Make Forth Small Again! Paul Rubin <no.email@nospam.invalid> - 2017-03-26 22:12 -0700
Re: Make Forth Small Again! "HAA" <someone@microsoft.com> - 2017-03-29 10:30 +1000
Re: Make Forth Small Again! anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-25 09:34 +0000
Re: Make Forth Small Again! mhx@iae.nl - 2017-03-25 03:46 -0700
Re: Make Forth Small Again! "HAA" <someone@microsoft.com> - 2017-03-27 10:56 +1000
Re: Make Forth Small Again! "HAA" <someone@microsoft.com> - 2017-03-28 10:07 +1000
Re: Make Forth Small Again! mhx@iae.nl - 2017-03-27 16:46 -0700
Re: Make Forth Small Again! Paul Rubin <no.email@nospam.invalid> - 2017-03-27 18:51 -0700
Re: Make Forth Small Again! "Elizabeth D. Rather" <erather@forth.com> - 2017-03-27 17:21 -1000
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-28 10:57 -0700
Re: Make Forth Small Again! minforth@arcor.de - 2017-03-28 01:16 -0700
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-28 03:36 -0500
Re: Make Forth Small Again! minforth@arcor.de - 2017-03-28 01:54 -0700
Re: Make Forth Small Again! "Elizabeth D. Rather" <erather@forth.com> - 2017-03-28 12:57 -1000
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-28 03:51 -0500
Re: Make Forth Small Again! "HAA" <someone@microsoft.com> - 2017-03-29 10:29 +1000
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-21 03:33 -0500
Re: Make Forth Small Again! Helmar Wodtke <helmwo@gmail.com> - 2017-03-21 05:17 -0700
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-21 09:42 -0500
Re: Make Forth Small Again! Helmar Wodtke <helmwo@gmail.com> - 2017-03-21 09:49 -0700
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-21 12:12 -0500
Re: Make Forth Small Again! Helmar Wodtke <helmwo@gmail.com> - 2017-03-21 10:28 -0700
Re: Make Forth Small Again! Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-03-21 16:43 -0400
Re: Make Forth Small Again! "Elizabeth D. Rather" <erather@forth.com> - 2017-03-21 14:11 -1000
Re: Make Forth Small Again! anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-21 16:46 +0000
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-21 12:32 -0500
Re: Make Forth Small Again! Helmar Wodtke <helmwo@gmail.com> - 2017-03-21 10:57 -0700
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-21 14:10 -0500
Re: Make Forth Small Again! Helmar Wodtke <helmwo@gmail.com> - 2017-03-21 12:50 -0700
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-21 15:29 -0500
Re: Make Forth Small Again! Helmar Wodtke <helmwo@gmail.com> - 2017-03-21 14:01 -0700
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-22 03:23 -0500
Re: Make Forth Small Again! Lars Brinkhoff <lars.spam@nocrew.org> - 2017-04-07 09:26 +0200
Re: Make Forth Small Again! "Elizabeth D. Rather" <erather@forth.com> - 2017-04-07 10:10 -1000
Re: Make Forth Small Again! Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-03-21 16:42 -0400
Re: Make Forth Small Again! anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-22 13:10 +0000
Re: Make Forth Small Again! Helmar Wodtke <helmwo@gmail.com> - 2017-03-22 06:38 -0700
Re: Make Forth Small Again! anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-22 15:24 +0000
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-22 08:52 -0500
Re: Make Forth Small Again! anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-25 13:55 +0000
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-25 17:41 -0500
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-22 07:43 -0700
Re: Make Forth Small Again! Helmar Wodtke <helmwo@gmail.com> - 2017-03-22 08:06 -0700
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-22 10:01 -0700
Re: Make Forth Small Again! Helmar Wodtke <helmwo@gmail.com> - 2017-03-22 10:19 -0700
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-22 10:59 -0700
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-22 18:31 +0000
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-22 13:55 -0700
Re: Make Forth Small Again! Mark Wills <markwills1970@gmail.com> - 2017-03-23 05:50 -0700
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-23 08:05 -0500
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-23 13:47 +0000
Re: Make Forth Small Again! Coos Haak <htrofhc@gmail.com> - 2017-03-23 15:31 +0100
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-23 10:25 -0500
Re: Make Forth Small Again! anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-24 18:07 +0000
Re: Make Forth Small Again! john <anon@example.com> - 2017-05-03 10:45 +0100
Re: Make Forth Small Again! Mark Wills <markwills1970@gmail.com> - 2017-05-03 03:50 -0700
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-03 05:57 -0500
Re: Make Forth Small Again! john <anon@example.com> - 2017-05-03 12:08 +0100
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-05-03 12:26 +0100
Re: Make Forth Small Again! john <anon@example.com> - 2017-05-03 16:02 +0100
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-05-03 16:08 +0100
Re: Make Forth Small Again! john <anon@example.com> - 2017-05-03 16:35 +0100
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-05-03 18:28 +0100
Re: Make Forth Small Again! john <anon@example.com> - 2017-05-04 10:14 +0100
Re: Make Forth Small Again! Coos Haak <htrofhc@gmail.com> - 2017-05-04 12:44 +0200
Re: Make Forth Small Again! john <anon@example.com> - 2017-05-04 12:32 +0100
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-04 06:49 -0500
Re: Make Forth Small Again! crc <charles.childers@gmail.com> - 2017-05-04 04:50 -0700
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-05-04 13:14 +0100
Re: Make Forth Small Again! john <anon@example.com> - 2017-05-05 11:19 +0100
Re: Make Forth Small Again! Julian Fondren <julian.fondren@gmail.com> - 2017-05-05 04:16 -0700
Re: Make Forth Small Again! john <anon@example.com> - 2017-05-05 12:35 +0100
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-05-03 13:55 -0700
Re: Make Forth Small Again! Cecil Bayona <cbayona@cbayona.com> - 2017-05-03 17:04 -0500
Re: Make Forth Small Again! Ron Aaron <rambamist@gmail.com> - 2017-05-04 07:29 +0300
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-04 02:52 -0500
Re: Make Forth Small Again! Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-05-04 05:08 -0400
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-05-04 06:34 -0500
Re: Make Forth Small Again! Cecil Bayona <cbayona@cbayona.com> - 2017-05-04 11:17 -0500
Re: Make Forth Small Again! Jan Coombs <jenfhaomndgfwutc@murmic.plus.com> - 2017-05-03 19:03 +0100
Re: Make Forth Small Again! anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-24 18:12 +0000
Re: Make Forth Small Again! anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-25 13:49 +0000
Re: Make Forth Small Again! Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-03-23 00:58 -0400
Re: Make Forth Small Again! Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-03-23 00:57 -0400
Re: Make Forth Small Again! "Elizabeth D. Rather" <erather@forth.com> - 2017-03-22 20:55 -1000
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-23 18:05 -0700
Re: Make Forth Small Again! rickman <gnuarm@gmail.com> - 2017-03-22 15:57 -0400
Re: Make Forth Small Again! anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-25 10:29 +0000
Re: Make Forth Small Again! Julian Fondren <julian.fondren@gmail.com> - 2017-03-25 04:00 -0700
Re: Make Forth Small Again! rickman <gnuarm@gmail.com> - 2017-05-03 08:01 -0400
Re: Make Forth Small Again! anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-05-04 16:06 +0000
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-22 14:02 -0700
Re: Make Forth Small Again! Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-03-23 00:57 -0400
Re: Make Forth Small Again! "Elizabeth D. Rather" <erather@forth.com> - 2017-03-22 20:59 -1000
Re: Make Forth Small Again! anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-23 12:14 +0000
Re: Make Forth Small Again! albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-03-23 14:45 +0100
Re: Make Forth Small Again! "Elizabeth D. Rather" <erather@forth.com> - 2017-03-23 12:24 -1000
Re: Make Forth Small Again! "HAA" <someone@microsoft.com> - 2017-03-28 10:55 +1000
Re: Make Forth Small Again! "Elizabeth D. Rather" <erather@forth.com> - 2017-03-27 17:24 -1000
Re: Make Forth Small Again! "HAA" <someone@microsoft.com> - 2017-03-29 10:49 +1000
Re: Make Forth Small Again! "Elizabeth D. Rather" <erather@forth.com> - 2017-03-28 15:05 -1000
Re: Make Forth Small Again! Julian Fondren <julian.fondren@gmail.com> - 2017-03-28 19:06 -0700
Re: Make Forth Small Again! Ron Aaron <rambamist@gmail.com> - 2017-03-29 06:43 +0300
Re: Make Forth Small Again! "HAA" <someone@microsoft.com> - 2017-03-30 10:37 +1000
Re: Make Forth Small Again! "Elizabeth D. Rather" <erather@forth.com> - 2017-03-29 19:34 -1000
Re: Make Forth Small Again! stephen@mpeforth.com (Stephen Pelc) - 2017-03-23 10:36 +0000
Re: Make Forth Small Again! anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-23 11:33 +0000
Re: Make Forth Small Again! albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-03-23 14:58 +0100
Re: Make Forth Small Again! anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-24 17:57 +0000
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-24 22:32 +0000
Re: Make Forth Small Again! Mark Wills <markwills1970@gmail.com> - 2017-03-24 17:10 -0700
Re: Make Forth Small Again! anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-03-25 07:31 +0000
Re: Make Forth Small Again! Lars Brinkhoff <lars.spam@nocrew.org> - 2017-04-07 08:50 +0200
Re: Make Forth Small Again! rickman <gnuarm@gmail.com> - 2017-03-20 17:57 -0400
Re: Make Forth Small Again! john <anon@example.com> - 2017-05-03 10:09 +0100
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-05-03 10:28 +0100
Re: Make Forth Small Again! rickman <gnuarm@gmail.com> - 2017-05-03 07:57 -0400
Re: Make Forth Small Again! stephen@mpeforth.com (Stephen Pelc) - 2017-05-03 13:07 +0000
Re: Make Forth Small Again! john <anon@example.com> - 2017-05-03 16:03 +0100
Re: Make Forth Small Again! "Elizabeth D. Rather" <erather@forth.com> - 2017-03-20 14:08 -1000
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-20 17:51 -0700
Re: Make Forth Small Again! minforth@arcor.de - 2017-03-20 13:12 -0700
Re: Make Forth Small Again! bruehlconsult@gmail.com - 2017-03-20 17:22 -0700
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-20 19:12 -0700
Re: Make Forth Small Again! Mark Wills <markwills1970@gmail.com> - 2017-03-21 02:30 -0700
Re: Make Forth Small Again! minforth@arcor.de - 2017-03-21 02:47 -0700
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-21 05:56 -0500
Re: Make Forth Small Again! rickman <gnuarm@gmail.com> - 2017-03-21 16:07 -0400
Re: Make Forth Small Again! "Elizabeth D. Rather" <erather@forth.com> - 2017-03-21 14:28 -1000
Re: Make Forth Small Again! "HAA" <someone@microsoft.com> - 2017-03-28 11:30 +1000
Re: Make Forth Small Again! Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-03-21 16:42 -0400
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-21 22:56 -0700
Re: Make Forth Small Again! Helmar Wodtke <helmwo@gmail.com> - 2017-03-22 04:04 -0700
Re: Make Forth Small Again! Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-03-23 00:57 -0400
Re: Make Forth Small Again! Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-03-24 02:32 -0700
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-24 10:00 +0000
Re: Make Forth Small Again! Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-03-24 06:46 -0700
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-24 14:41 +0000
Re: Make Forth Small Again! Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-03-25 15:32 -0700
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-25 23:10 +0000
Re: Make Forth Small Again! Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-03-25 17:29 -0700
Re: Make Forth Small Again! Paul Rubin <no.email@nospam.invalid> - 2017-03-25 18:08 -0700
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-26 08:30 +0100
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-26 08:50 +0100
Re: Make Forth Small Again! Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-03-26 15:14 -0700
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-27 08:32 +0100
Re: Make Forth Small Again! Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-03-30 13:21 -0700
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-27 15:31 +0100
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-27 09:04 -0700
Re: Make Forth Small Again! Cecil Bayona <cbayona@cbayona.com> - 2017-03-27 11:52 -0500
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-27 18:41 +0100
Re: Make Forth Small Again! Cecil Bayona <cbayona@cbayona.com> - 2017-03-27 12:58 -0500
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-27 12:07 -0700
Re: Make Forth Small Again! foxaudioresearch@gmail.com - 2017-03-27 13:06 -0700
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-28 11:30 -0700
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-28 20:06 +0100
Re: Make Forth Small Again! albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-03-29 14:54 +0200
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-30 19:13 -0700
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-27 21:18 +0100
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-28 10:54 -0700
Re: Make Forth Small Again! Ron Aaron <rambamist@gmail.com> - 2017-03-27 21:53 +0300
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-27 22:29 +0100
Re: Make Forth Small Again! Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-03-30 14:07 -0700
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-30 16:03 -0700
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-31 09:28 +0100
Re: Make Forth Small Again! Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-03-31 03:36 -0700
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-31 19:29 -0700
Re: Make Forth Small Again! Mark Wills <markwills1970@gmail.com> - 2017-04-01 04:37 -0700
Re: Make Forth Small Again! Paul Rubin <no.email@nospam.invalid> - 2017-04-01 09:23 -0700
Re: Make Forth Small Again! Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-04-01 10:37 -0700
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-04-01 11:55 -0500
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-04-01 14:15 -0700
Re: Make Forth Small Again! Brad Eckert <hwfwguy@gmail.com> - 2017-05-06 12:55 -0700
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-05-07 12:08 +0100
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-05-07 09:04 -0700
Re: Make Forth Small Again! Coos Haak <htrofhc@gmail.com> - 2017-04-01 21:35 +0200
Re: Make Forth Small Again! Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-04-01 20:35 -0400
Re: Make Forth Small Again! Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-04-01 11:52 -0700
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-04-01 16:31 -0700
Re: Make Forth Small Again! Julian Fondren <julian.fondren@gmail.com> - 2017-04-01 20:54 -0700
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-04-01 21:13 -0700
Re: Make Forth Small Again! Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-04-05 16:06 -0700
Re: Make Forth Small Again! Alex <alex@rivadpm.com> - 2017-03-31 09:42 +0100
Re: Make Forth Small Again! Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-03-31 03:52 -0700
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-30 20:26 -0700
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-27 04:55 -0500
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-27 08:49 -0700
Re: Make Forth Small Again! Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-03-30 13:35 -0700
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-30 14:23 -0700
Re: Make Forth Small Again! Julian Fondren <julian.fondren@gmail.com> - 2017-03-30 15:28 -0700
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-30 23:20 -0700
Re: Make Forth Small Again! Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-03-31 02:29 -0700
Re: Make Forth Small Again! Julian Fondren <julian.fondren@gmail.com> - 2017-03-31 03:20 -0700
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-31 03:38 -0500
Re: Make Forth Small Again! Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-03-24 09:17 -0500
Re: Make Forth Small Again! hughaguilar96@gmail.com - 2017-03-24 17:52 -0700
Page 7 of 11 — ← Prev page 1 … 5 6 [7] 8 9 … 11 Next page →
| From | "Elizabeth D. Rather" <erather@forth.com> |
|---|---|
| Date | 2017-03-29 19:34 -1000 |
| Message-ID | <kuGdnVenru1LBUHFnZ2dnUU7-I_NnZ2d@supernews.com> |
| In reply to | #56469 |
On 3/29/17 2:37 PM, HAA wrote: > Julian Fondren wrote: >> On Tuesday, March 28, 2017 at 8:05:49 PM UTC-5, Elizabeth D. Rather wrote: >>> >>> Sorry, it's not at all clear to me what the problem is. >>> >> >> The problem is that 3.14159e is truncated when Forth-94 says it >> should round to nearest, which would result in "31416" > > Correct. Some background. As originally coded by Forth Inc REPRESENT > *did* in fact round. But it relied on F>D rounding, which was non-compliant. > When Forth Inc subsequently corrected F>D, they didn't update REPRESENT. > All explained in my bug report some years ago. > > The quick fix is to change the line: > > #EXP DUP >R - 1- >10** DROP F>D <# #S #> > > to: > > #EXP DUP >R - 1- >10** DROP FROUND F>D <# #S #> I sent this to Leon, and he reports back that he fixed it and the fix will be in the next SwiftForth maintenance release. He expresses amazement that no one ever reported it. In fact, he searched the support emails back to 2006, and found nothing. Was your report before that? So, thank to you guys for reporting it... next time, tell support@forth.com! Cheers, Elizabeth -- Elizabeth R. Conklin FORTH, Inc. 6080 Center Drive, Suite 600 Los Angeles, CA 90045 USA
[toc] | [prev] | [next] | [standalone]
| From | stephen@mpeforth.com (Stephen Pelc) |
|---|---|
| Date | 2017-03-23 10:36 +0000 |
| Message-ID | <58d3a487.630696894@news.eternal-september.org> |
| In reply to | #56159 |
On Thu, 23 Mar 2017 00:57:55 -0400, Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> wrote: >I'm aghast! Why is there no check for that? It's clearly the >problem of the system implementer since it couldn't possibly be the >domain of the user coder ... Oh, yes. Which of the three float packs do you need with VFX? That's why one is not pre-compiled. Stephen -- Stephen Pelc, stephenXXX@mpeforth.com MicroProcessor Engineering Ltd - More Real, Less Time 133 Hill Lane, Southampton SO15 5AF, England tel: +44 (0)23 8063 1441, fax: +44 (0)23 8033 9691 web: http://www.mpeforth.com - free VFX Forth downloads
[toc] | [prev] | [next] | [standalone]
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2017-03-23 11:33 +0000 |
| Message-ID | <2017Mar23.123308@mips.complang.tuwien.ac.at> |
| In reply to | #56168 |
stephen@mpeforth.com (Stephen Pelc) writes:
>Which of the three float packs do you need with VFX?
If I don't ask for a particular one, the one that you deem the most
appropriate.
>That's why one is not pre-compiled.
Not a good reason. Alternatives are:
1) Have a default one pre-compiled, and if somebody needs a different
one, he can load that one. The procompiled one is then shadowed and
costs a little memory, but that's all.
2) Compile a default pack if the program performs
s" floating" environment?
and no FP pack is loaded. If a program needs a specific pack, it can
load it before (or instead of) making that query. Alternatively,
compile the default pack if a float word is used and no specific pack
has been loaded (i.e., what Albert van der Horst is advocating).
3) Have an executable "vfxlin" that has the default FP pack
precompiled, and "vfxlin-nf" that misses the FP pack.
4) "vfxlin" compiles the default FP pack on startup unless the user
invokes it with the flag "-nofloat".
There are probably more options.
- 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 2016: http://www.euroforth.org/ef16/
[toc] | [prev] | [next] | [standalone]
| From | albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) |
|---|---|
| Date | 2017-03-23 14:58 +0100 |
| Message-ID | <ob0k9n$s8p$1@cherry.spenarnc.xs4all.nl> |
| In reply to | #56169 |
In article <2017Mar23.123308@mips.complang.tuwien.ac.at>,
Anton Ertl <anton@mips.complang.tuwien.ac.at> wrote:
>stephen@mpeforth.com (Stephen Pelc) writes:
>>Which of the three float packs do you need with VFX?
>
>If I don't ask for a particular one, the one that you deem the most
>appropriate.
>
>>That's why one is not pre-compiled.
>
>Not a good reason. Alternatives are:
>
>1) Have a default one pre-compiled, and if somebody needs a different
>one, he can load that one. The procompiled one is then shadowed and
>costs a little memory, but that's all.
>
>2) Compile a default pack if the program performs
>
> s" floating" environment?
( "floating" WANTED makes more sense if you want this.)
>
>and no FP pack is loaded. If a program needs a specific pack, it can
>load it before (or instead of) making that query. Alternatively,
>compile the default pack if a float word is used and no specific pack
>has been loaded (i.e., what Albert van der Horst is advocating).
Well, I could, but I require a conscious effort to add floating point.
If I mistype PI then I don't want to load the fp package which could
take minutes on MSDOS, or would lead to out of memory on a connected
SBC.
You set me on the right trail with this discussion though.
lina -r
would be the way to start a Forth where you want real numbers from
the getgo.
>
>3) Have an executable "vfxlin" that has the default FP pack
>precompiled, and "vfxlin-nf" that misses the FP pack.
>
>4) "vfxlin" compiles the default FP pack on startup unless the user
>invokes it with the flag "-nofloat".
>
>There are probably more options.
You missed an obvious one
5) "vfxlin" compiles the default FP pack on startup if the user
invokes it with the flag "-float".
Then you could set
alias vfxlin='vxflin -float'
in your profile and would be happy, probably.
Groetjes Albert
>- anton
--
Albert van der Horst, UTRECHT,THE NETHERLANDS
Economic growth -- being exponential -- ultimately falters.
albert@spe&ar&c.xs4all.nl &=n http://home.hccnet.nl/a.w.m.van.der.horst
[toc] | [prev] | [next] | [standalone]
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2017-03-24 17:57 +0000 |
| Message-ID | <2017Mar24.185759@mips.complang.tuwien.ac.at> |
| In reply to | #56177 |
albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) writes:
>In article <2017Mar23.123308@mips.complang.tuwien.ac.at>,
>Anton Ertl <anton@mips.complang.tuwien.ac.at> wrote:
>>2) Compile a default pack if the program performs
>>
>> s" floating" environment?
>
>( "floating" WANTED makes more sense if you want this.)
Let's see:
[~:93447] sf
SwiftForth i386-Linux 3.6.3 29-Jun-2016
s" floating" environment? ok
"floating" WANTED "floating" ?
[~:93448] vfxlin
VFX Forth for Linux IA32 Version: 4.72 [build 0555]
s" floating" environment? ok-1
"floating" WANTED
Err# -13 ERR: Undefined word.
-> "floating" WANTED
^
bye [~:93449] gforth
Gforth 0.7.2, Copyright (C) 1995-2008 Free Software Foundation, Inc.
Gforth comes with ABSOLUTELY NO WARRANTY; for details type `license'
Type `bye' to exit
s" floating" environment? ok
"floating" WANTED
:2: Undefined word
>>>"floating"<<< WANTED
Conclusion: hooking it into ENVIRONMENT? makes more sense, because all
Forth-94 and Forth-2012 systems already have this word, even if they
don't provide the functionality of loading the wordset if it is not
already present.
>5) "vfxlin" compiles the default FP pack on startup if the user
>invokes it with the flag "-float".
Not as good as the other options, but better than the arcane
invocation needed now.
- 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 2016: http://www.euroforth.org/ef16/
[toc] | [prev] | [next] | [standalone]
| From | Alex <alex@rivadpm.com> |
|---|---|
| Date | 2017-03-24 22:32 +0000 |
| Message-ID | <ob46kd$epq$1@dont-email.me> |
| In reply to | #56232 |
On 3/24/2017 17:57, Anton Ertl wrote: > albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) writes: >> In article <2017Mar23.123308@mips.complang.tuwien.ac.at>, >> Anton Ertl <anton@mips.complang.tuwien.ac.at> wrote: >>> 2) Compile a default pack if the program performs >>> >>> s" floating" environment? >> >> ( "floating" WANTED makes more sense if you want this.) > > Let's see: > > [~:93447] sf > SwiftForth i386-Linux 3.6.3 29-Jun-2016 > s" floating" environment? ok > "floating" WANTED "floating" ? > > [~:93448] vfxlin > VFX Forth for Linux IA32 Version: 4.72 [build 0555] > s" floating" environment? ok-1 > "floating" WANTED > Err# -13 ERR: Undefined word. > -> "floating" WANTED > ^ > bye [~:93449] gforth > Gforth 0.7.2, Copyright (C) 1995-2008 Free Software Foundation, Inc. > Gforth comes with ABSOLUTELY NO WARRANTY; for details type `license' > Type `bye' to exit > s" floating" environment? ok > "floating" WANTED > :2: Undefined word > >>>"floating"<<< WANTED > > Conclusion: hooking it into ENVIRONMENT? makes more sense, because all > Forth-94 and Forth-2012 systems already have this word, even if they > don't provide the functionality of loading the wordset if it is not > already present. > >> 5) "vfxlin" compiles the default FP pack on startup if the user >> invokes it with the flag "-float". > > Not as good as the other options, but better than the arcane > invocation needed now. > > - anton > http://www.forth200x.org/documents/forth16-1.pdf This standard designates the following practice as obsolescent: – Using ENVIRONMENT? to enquire whether a word set is present. -- Alex
[toc] | [prev] | [next] | [standalone]
| From | Mark Wills <markwills1970@gmail.com> |
|---|---|
| Date | 2017-03-24 17:10 -0700 |
| Message-ID | <4011f2b2-b96c-4b74-aabe-55a090642c92@googlegroups.com> |
| In reply to | #56245 |
Good. It is/was a terrible idea. Should have used bit field. Would have been so much easier.
[toc] | [prev] | [next] | [standalone]
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2017-03-25 07:31 +0000 |
| Message-ID | <2017Mar25.083127@mips.complang.tuwien.ac.at> |
| In reply to | #56245 |
Alex <alex@rivadpm.com> writes:
>On 3/24/2017 17:57, Anton Ertl wrote:
>> albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) writes:
>>> In article <2017Mar23.123308@mips.complang.tuwien.ac.at>,
>>> Anton Ertl <anton@mips.complang.tuwien.ac.at> wrote:
>>>> 2) Compile a default pack if the program performs
>>>>
>>>> s" floating" environment?
...
>http://www.forth200x.org/documents/forth16-1.pdf
>
>This standard designates the following practice as obsolescent:
>– Using ENVIRONMENT? to enquire whether a word set is present.
Doesn't really matter in the present context. Even when the
"floating" query is finally de-standardized, a standard system may or
may not load its FP words when it sees that query, just as now.
The only thing that de-standardization will change is that a system
may then implement a "floating" query that gives arbitrary results;
e.g., the query above might return -1 -1 even though the system does
not implement the floating-point words in any form. It's unlikely
that any systems will actually do this, though.
Also, if systems actually implemented the "floating" query in the way
described above, and programs then use it because it avoids the
non-standardized and arcane invocations for loading the floating-point
words, we could decide to keep the "floating" query in the standard.
- 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 2016: http://www.euroforth.org/ef16/
[toc] | [prev] | [next] | [standalone]
| From | Lars Brinkhoff <lars.spam@nocrew.org> |
|---|---|
| Date | 2017-04-07 08:50 +0200 |
| Message-ID | <86h9204spb.fsf@molnjunk.nocrew.org> |
| In reply to | #55995 |
Andrew Haley wrote: > There seems to be an odd misunderstanding about the meaning of "core". > Some people think that because a word is in CORE it has to be in the > set of words which is always loaded into the system, and it must be > present in the predefined dictionary when Forth starts. There's also the distiction between kernel and core. Even though it might be desirable to have all of CORE available from start, they don't have to be in the kernel. In my (admittely toy) Forth, the kernel is very spartan and only has the definitions needed to read and compile files. I have much of CORE loaded from source. If space were thight, I could remove definitions from core.fth.
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2017-03-20 17:57 -0400 |
| Message-ID | <oapj25$oav$1@dont-email.me> |
| In reply to | #55969 |
On 3/20/2017 1:34 PM, Paul Rubin wrote: > Helmar Wodtke <helmwo@gmail.com> writes: >> Forth has to become SMALL again. Something basic. Well, even if this >> is not convenient to some commercial vendors: Forth lost with its >> complexity. Instead of DPAN94 there should be something that *only* >> defines DUP DROP SWAP etc. > > Would you use it? What would use it for? > >> Inside "core"-word of DPANS is for example 2OVER... Why? Today? > > That does surprise me but I checked and you're right. I would have > expected 2over to be in the optional double-number extension. You are not required to implement every word in the standard, even the CORE. 5.1.1 System compliance "A system that complies with all the system requirements given in sections 3 Usage requirements and 4.1 System documentation and their sub-sections is a Standard System. An otherwise Standard System that provides only a portion of the Core words is a Standard System Subset." Go Forth and prosper. If thine word offends thee, pluck it out! Why is everyone so down on the ANS standard? Some say it does too much, others say it does too little. ANS is what it is. Take What You Need and Leave the Rest -- Rick C
[toc] | [prev] | [next] | [standalone]
| From | john <anon@example.com> |
|---|---|
| Date | 2017-05-03 10:09 +0100 |
| Message-ID | <MPG.3373ae92809e594f989714@news.virginmedia.com> |
| In reply to | #55976 |
In article <oapj25$oav$1@dont-email.me>, gnuarm@gmail.com says... > > You are not required to implement every word in the standard, even the > CORE. > > If a standard says this the standard is broken. -- john ========================= http://johntech.co.uk "Bleeding Edge Forum" http://johntech.co.uk/forum/ =========================
[toc] | [prev] | [next] | [standalone]
| From | Alex <alex@rivadpm.com> |
|---|---|
| Date | 2017-05-03 10:28 +0100 |
| Message-ID | <oec7mj$rg0$1@dont-email.me> |
| In reply to | #58559 |
On 5/3/2017 10:09, john wrote: > In article <oapj25$oav$1@dont-email.me>, gnuarm@gmail.com says... >> >> You are not required to implement every word in the standard, even the >> CORE. >> >> > > If a standard says this the standard is broken. > It's always best to go back to the standard. It says ------- 5.1.1 System compliance A system that complies with all the system requirements given in sections 3. Usage requirements and 4.1 System documentation and their sub-sections is a Standard System. An otherwise Standard System that provides only a portion of the Core words is a Standard System Subset. An otherwise Standard System (Subset) that fails to comply with one or more of the minimum values or ranges specified in 3. Usage requirements and its sub-sections has environmental restrictions. 5.1.2 System labeling A Standard System (Subset) shall be labeled an ANS Forth System (Subset). That label, by itself, shall not be applied to Standard Systems or Standard System Subsets that have environmental restrictions. The phrase with Environmental Restrictions shall be appended to the label of a Standard System (Subset) that has environmental restrictions. The phrase Providing name(s) from the Core Extensions word set shall be appended to the label of any Standard System that provides portions of the Core Extensions word set. The phrase Providing the Core Extensions word set shall be appended to the label of any Standard System that provides all of the Core Extensions word set. A system that doesn't implement all of CORE is therefore a Standard System Subset. ------- Why would you consider that broken? -- Alex
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2017-05-03 07:57 -0400 |
| Message-ID | <oecgcm$tub$1@dont-email.me> |
| In reply to | #58559 |
On 5/3/2017 5:09 AM, john wrote: > In article <oapj25$oav$1@dont-email.me>, gnuarm@gmail.com says... >> >> You are not required to implement every word in the standard, even the >> CORE. >> >> > > If a standard says this the standard is broken. It's broken according to what standard? Every system is required to have a document that tells a user what the system includes and what it does not. There are many words that while being in the CORE or CORE EXT parts of the standard, may not be needed in every system. Why require them to be in a system that won't use them? -- Rick C
[toc] | [prev] | [next] | [standalone]
| From | stephen@mpeforth.com (Stephen Pelc) |
|---|---|
| Date | 2017-05-03 13:07 +0000 |
| Message-ID | <5909d36f.602971663@news.eternal-september.org> |
| In reply to | #58559 |
On Wed, 3 May 2017 10:09:12 +0100, john <anon@example.com> wrote: >In article <oapj25$oav$1@dont-email.me>, gnuarm@gmail.com says... >> >> You are not required to implement every word in the standard, even the >> CORE. > >If a standard says this the standard is broken. The standard only says that the word hould be available. Making it available as source code is fine. This has been the understanding and situation since the ANS standard first appeared in 1994. The "supply code as source" situation has been misunderstood or ignored for many years. I don't know of any Forth standards committee members who want to change the situation. You are free to make a proposal with new wording. Stephen -- Stephen Pelc, stephenXXX@mpeforth.com MicroProcessor Engineering Ltd - More Real, Less Time 133 Hill Lane, Southampton SO15 5AF, England tel: +44 (0)23 8063 1441, fax: +44 (0)23 8033 9691 web: http://www.mpeforth.com - free VFX Forth downloads
[toc] | [prev] | [next] | [standalone]
| From | john <anon@example.com> |
|---|---|
| Date | 2017-05-03 16:03 +0100 |
| Message-ID | <MPG.337401aec007933b98971a@news.virginmedia.com> |
| In reply to | #58581 |
In article <5909d36f.602971663@news.eternal-september.org>, stephen@mpeforth.com says... > > You are free to make a proposal with new wording. > > Stephen > > The post I responded to was incomplete. Exceptions and labeling were not mentioned hence the absolute comment. The sort of sloppy acceptance of lazy behaviour being promoted here is frightening in the extreme. Hence my input. -- john ========================= http://johntech.co.uk "Bleeding Edge Forum" http://johntech.co.uk/forum/ =========================
[toc] | [prev] | [next] | [standalone]
| From | "Elizabeth D. Rather" <erather@forth.com> |
|---|---|
| Date | 2017-03-20 14:08 -1000 |
| Message-ID | <e-ydnYPNrpF3803FnZ2dnUU7-VvNnZ2d@supernews.com> |
| In reply to | #55969 |
On 3/20/17 7:34 AM, Paul Rubin wrote: > Helmar Wodtke <helmwo@gmail.com> writes: >> Forth has to become SMALL again. Something basic. Well, even if this >> is not convenient to some commercial vendors: Forth lost with its >> complexity. Instead of DPAN94 there should be something that *only* >> defines DUP DROP SWAP etc. > > Would you use it? What would use it for? > >> Inside "core"-word of DPANS is for example 2OVER... Why? Today? > > That does surprise me but I checked and you're right. I would have > expected 2over to be in the optional double-number extension. Because the 2's operators are useful for pairs of numbers, in applications that don't have any double-precision numbers. Forth does a lot with pairs of numbers, such as addr-len string operands, x/y coordinates, etc. These operators are great in many situations. Cheers, Elizabeth -- Elizabeth R. Conklin FORTH, Inc. 6080 Center Drive, Suite 600 Los Angeles, CA 90045 USA
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2017-03-20 17:51 -0700 |
| Message-ID | <9c4ba433-9c0b-4f85-9d50-0a38970527d5@googlegroups.com> |
| In reply to | #55981 |
On Monday, March 20, 2017 at 5:08:16 PM UTC-7, Elizabeth D. Rather wrote: > On 3/20/17 7:34 AM, Paul Rubin wrote: > > Helmar Wodtke <helmwo@gmail.com> writes: > >> Inside "core"-word of DPANS is for example 2OVER... Why? Today? > > > > That does surprise me but I checked and you're right. I would have > > expected 2over to be in the optional double-number extension. > > Because the 2's operators are useful for pairs of numbers, in > applications that don't have any double-precision numbers. Forth does a > lot with pairs of numbers, such as addr-len string operands, x/y > coordinates, etc. These operators are great in many situations. A major problem with ANS-Forth is that we have different sized data intermixed on the data-stack. For example, we have both single-precision integers (one cell) and double-precision integers (two cells). This results in a lot of complicated stack-juggling. I don't do this in Straight Forth. I have a single-cell stack and a double-cell stack. The function S>D pops a value from the single-cell stack and pushes a value to the double-cell stack. The function UM* pops two values from the single-cell stack and pushes a value to the double-cell stack. The function UM/MOD pops a value from the double-cell stack (the numerator) and pops a value from the single-cell stack (the denominator), then pushes two values to the single-cell stack (the remainder and quotient). Similarly, I don't have adr/cnt pairs on the data-stack representing strings. I have a string-stack where all work with strings is done. The string-stack is a double-cell stack internally because it has the adr and cnt values. I originally believed that I could use the double-cell stack (which is used for double-precision numbers and ratios) for strings too. Then I wrote my STRING-STACK.4TH package and figured out the copy-on-write (COW) idea. At this time I realized that I couldn't have strings mixed together with numeric data (double-precision integers and ratios) because when my FIX-DERIVATIVES function searches the stack for derivative strings, it would be unable to distinguish between strings and numeric data --- so, I need a separate stack for strings. ANS-Forth is really 1970s technology. Why didn't Charles Moore have a single-cell stack and a double-cell stack, and maybe a string-stack too? Well, the PDP-11 has only 8 registers, so there wasn't enough registers available for all of these stack pointers. Why didn't Charles Moore have local variables? Well, the PDP-11 has only 8 registers, so there wasn't enough registers available for a local-frame pointer (humorously, SwiftForth doesn't use a register for the local-frame pointer, but instead uses a user variable, which is why locals are abysmally slow in SwiftForth). All in all, ANS-Forth appears to have been designed for the PDP-11. We have all of these weird and stupid restrictions, such as having only one data-stack, that only make sense on the PDP-11. There are no programmers at Forth Inc.. All they have there are "maintenance programmers" who have spent decades maintaining Charles Moores old code from the 1970s. They aren't adding any value at all. They made ANS-Forth essentially a description of Charles Moore's 1970s MicroForth. Even today, in 2017, Elizabeth Rather strives to hold the Forth community down at this level --- keep us all in the 1970s forever...
[toc] | [prev] | [next] | [standalone]
| From | minforth@arcor.de |
|---|---|
| Date | 2017-03-20 13:12 -0700 |
| Message-ID | <3523fbb4-cc14-43d3-9b8a-15f8f98bd06b@googlegroups.com> |
| In reply to | #55968 |
Am Montag, 20. März 2017 17:58:20 UTC+1 schrieb Helmar Wodtke: > Well, I did not reply to BIG/GREAT ;) > > Most people think that GREAT is some BIGger advanture, what a Forth system has to offer. > > What do you expect? A GUI-API? What number of GUIs has Forth survived? How complicated it is, to connect Forth to any user interface? > > Do you really want a "BUTTON" ( gui x y w h s -- gui' ) word defined in standard? > > Forth has to become SMALL again. Something basic. Well, even if this is not convenient to some commercial vendors: Forth lost with its complexity. Instead of DPAN94 there should be something that *only* defines DUP DROP SWAP etc. Inside "core"-word of DPANS is for example 2OVER... Why? Today? 64bit... Or all these 8-bit-memory access? All crap. Nobody needs this. Americans can use it. But to get U-Umlaut is a problem in current "standards". > > Regards, > -Helmar *grin* sounds like too many bears passed thru some kidneys... in the end Forth is best at creating DSLs. that spells DOMAIN specific languages. so one can rant at Forth at one's heart's content when paddling in anther domain.
[toc] | [prev] | [next] | [standalone]
| From | bruehlconsult@gmail.com |
|---|---|
| Date | 2017-03-20 17:22 -0700 |
| Message-ID | <d6a79b25-a4cb-4d9c-ad88-22d0e0643f9f@googlegroups.com> |
| In reply to | #55968 |
On Monday, March 20, 2017 at 12:58:20 PM UTC-4, Helmar Wodtke wrote: > Well, I did not reply to BIG/GREAT ;) > > Most people think that GREAT is some BIGger advanture, what a Forth system has to offer. > > What do you expect? A GUI-API? What number of GUIs has Forth survived? How complicated it is, to connect Forth to any user interface? > > Do you really want a "BUTTON" ( gui x y w h s -- gui' ) word defined in standard? > > Forth has to become SMALL again. Something basic. Well, even if this is not convenient to some commercial vendors: Forth lost with its complexity. Instead of DPAN94 there should be something that *only* defines DUP DROP SWAP etc. Inside "core"-word of DPANS is for example 2OVER... Why? Today? 64bit... Or all these 8-bit-memory access? All crap. Nobody needs this. Americans can use it. But to get U-Umlaut is a problem in current "standards". > > Regards, > -Helmar If you like to have GUIs, there is VisualForth: http://www.visualforth.org/ GUIs are made in a drag and drop manor, everything else is programmed in plain Win32Forth.
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2017-03-20 19:12 -0700 |
| Message-ID | <563f58e3-02b2-481f-b61a-d76f1fdd4833@googlegroups.com> |
| In reply to | #55968 |
On Monday, March 20, 2017 at 9:58:20 AM UTC-7, Helmar Wodtke wrote: > Well, I did not reply to BIG/GREAT ;) > > Most people think that GREAT is some BIGger advanture, what a Forth system has to offer. > > What do you expect? A GUI-API? What number of GUIs has Forth survived? How complicated it is, to connect Forth to any user interface? > > Do you really want a "BUTTON" ( gui x y w h s -- gui' ) word defined in standard? > > Forth has to become SMALL again. Something basic. Well, even if this is not convenient to some commercial vendors: Forth lost with its complexity. Instead of DPAN94 there should be something that *only* defines DUP DROP SWAP etc. Inside "core"-word of DPANS is for example 2OVER... Why? Today? 64bit... Or all these 8-bit-memory access? All crap. Nobody needs this. Americans can use it. But to get U-Umlaut is a problem in current "standards". > > Regards, > -Helmar How about: "Make Forth Sane Again!" With my Straight Forth design, I am getting rid of a lot of cruft. I don't have DO loops anymore, for example. So, small is beautiful! On the other hand, I am adding two data-structures --- the array and the chain --- I expect maybe 99% of the programs to use these, and only 1% to have custom data-structures. So, big is beautiful! I agree that we don't want to put a GUI code-library in the standard --- it should be possible to write code-libraries such as this in the standard --- it would be best to write versions for every OS that the system might be running on, so it will require somebody who knows a lot (knows more than I do). OTOH, some words are very useful --- an example is TICKS that gives the current time in milliseconds --- something like this would be difficult for the user to write, as it would require knowledge of every OS that the system might be running on. I might also have graphics capability built into the language --- that seems useful to everybody --- unfortunately, this is somewhat beyond my knowledge-level (a lot of useful programming is beyond my knowledge-level).
[toc] | [prev] | [next] | [standalone]
Page 7 of 11 — ← Prev page 1 … 5 6 [7] 8 9 … 11 Next page →
Back to top | Article view | comp.lang.forth
csiph-web