Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #53455 > unrolled thread
| Started by | awegel@arcor.de (Alexander Wegel) |
|---|---|
| First post | 2016-12-21 01:19 +0100 |
| Last post | 2017-01-08 16:55 -0800 |
| Articles | 20 on this page of 266 — 26 participants |
Back to article view | Back to comp.lang.forth
"Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2016-12-21 01:19 +0100
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2016-12-24 05:40 -0600
Re: "Hello world" using Hughs novice package Julian Fondren <julian.fondren@gmail.com> - 2016-12-24 06:01 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2016-12-25 19:27 +0100
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-26 18:16 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2016-12-27 14:27 +0100
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2016-12-27 14:29 +0100
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2016-12-27 14:27 +0100
Re: "Hello world" using Hughs novice package "HAA" <someone@microsoft.com> - 2016-12-28 11:35 +1100
Re: "Hello world" using Hughs novice package Paul Rubin <no.email@nospam.invalid> - 2016-12-27 17:38 -0800
Re: "Hello world" using Hughs novice package "HAA" <someone@microsoft.com> - 2016-12-29 10:11 +1100
Re: "Hello world" using Hughs novice package "Elizabeth D. Rather" <erather@forth.com> - 2016-12-29 17:06 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2016-12-28 05:39 +0100
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-27 22:37 -0800
Re: "Hello world" using Hughs novice package crc <charles.childers@gmail.com> - 2016-12-28 05:40 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-28 23:03 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2016-12-30 20:54 +0100
Re: "Hello world" using Hughs novice package Coos Haak <htrofhc@gmail.com> - 2017-01-02 20:17 +0100
Re: "Hello world" using Hughs novice package mhx@iae.nl - 2017-01-02 12:22 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2017-01-02 22:08 +0100
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-02 21:40 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2017-01-03 13:51 +0100
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-03 21:51 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-06 19:36 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2017-01-07 14:55 +0100
Re: "Hello world" using Hughs novice package albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-01-07 19:01 +0100
Re: "Hello world" using Hughs novice package Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2017-01-08 12:06 +0000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-08 16:46 -0800
Re: "Hello world" using Hughs novice package "Robert L." <No_spamming@noWhere_7073.org> - 2017-01-03 15:59 +0000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-27 23:12 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2016-12-30 20:54 +0100
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2016-12-28 04:57 -0600
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2016-12-28 11:23 +0000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-28 23:16 -0800
Re: "Hello world" using Hughs novice package Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2016-12-30 16:31 +0000
Re: "Hello world" using Hughs novice package "David N. Williams" <williams@umich.edu> - 2016-12-30 15:21 -0500
Re: "Hello world" using Hughs novice package Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2017-01-05 12:00 +0000
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2017-01-05 13:30 +0100
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-05 17:32 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2017-01-06 02:50 +0100
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-05 18:20 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-06 17:58 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2017-01-07 14:55 +0100
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-05 16:15 +0000
Re: "Hello world" using Hughs novice package Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2017-01-10 08:43 +0000
Re: "Hello world" using Hughs novice package Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2016-12-30 14:37 +0000
Re: "Hello world" using Hughs novice package john <anon@example.com> - 2016-12-30 15:57 +0000
Re: "Hello world" using Hughs novice package Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2016-12-30 17:19 +0000
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2016-12-30 21:10 +0000
Re: "Hello world" using Hughs novice package "Elizabeth D. Rather" <erather@forth.com> - 2016-12-30 12:44 -1000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-30 15:43 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2016-12-31 00:09 +0000
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-03 17:25 +0000
Re: "Hello world" using Hughs novice package john <anon@example.com> - 2016-12-30 22:47 +0000
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2016-12-31 03:31 -0600
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2016-12-30 15:46 +0000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-30 15:05 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2016-12-31 00:26 +0000
Re: "Hello world" using Hughs novice package "HAA" <someone@microsoft.com> - 2016-12-31 11:49 +1100
Re: "Hello world" using Hughs novice package "Elizabeth D. Rather" <erather@forth.com> - 2016-12-30 15:21 -1000
Re: "Hello world" using Hughs novice package "HAA" <someone@microsoft.com> - 2017-01-02 11:11 +1100
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-02 00:28 +0000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-01 17:45 -0800
Re: "Hello world" using Hughs novice package "Elizabeth D. Rather" <erather@forth.com> - 2017-01-01 20:57 -1000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-02 06:55 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-02 10:44 +0000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-02 07:01 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-02 15:46 +0000
Re: "Hello world" using Hughs novice package john <anon@example.com> - 2017-01-02 16:54 +0000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-02 10:23 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-02 10:06 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-02 19:13 +0000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-02 14:08 -0800
Re: "Hello world" using Hughs novice package mhx@iae.nl - 2017-01-02 14:46 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-02 17:10 -0800
Re: "Hello world" using Hughs novice package "Elizabeth D. Rather" <erather@forth.com> - 2017-01-02 21:58 -1000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-03 15:54 -0800
Re: "Hello world" using Hughs novice package JUERGEN <epldfpga@aol.com> - 2017-01-04 06:21 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-04 11:19 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2017-01-04 22:34 +0100
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-04 14:44 -0800
Re: "Hello world" using Hughs novice package JUERGEN <epldfpga@aol.com> - 2017-01-04 15:13 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-05 08:18 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-04 23:17 +0000
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-05 04:15 -0600
Re: "Hello world" using Hughs novice package mhx@iae.nl - 2017-01-08 01:18 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-08 15:52 -0800
Re: "Hello world" using Hughs novice package "Elizabeth D. Rather" <erather@forth.com> - 2017-01-08 21:00 -1000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-09 15:58 -0800
Re: "Hello world" using Hughs novice package Paul Rubin <no.email@nospam.invalid> - 2017-01-09 17:39 -0800
Re: "Hello world" using Hughs novice package "Elizabeth D. Rather" <erather@forth.com> - 2017-01-09 18:53 -1000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-12 06:27 -0800
Re: "Hello world" using Hughs novice package "Elizabeth D. Rather" <erather@forth.com> - 2017-01-12 13:44 -1000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-12 17:36 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-13 03:17 -0600
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-13 14:44 +0000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-13 14:43 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-14 00:23 +0000
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-14 11:52 +0000
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-14 16:00 +0000
Re: "Hello world" using Hughs novice package Paul Rubin <no.email@nospam.invalid> - 2017-01-14 11:51 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-14 15:06 -0800
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-15 14:54 +0000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-15 13:33 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-13 16:06 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-14 00:25 +0000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-13 18:00 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-13 22:17 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-13 16:04 -0800
Re: "Hello world" using Hughs novice package "Elizabeth D. Rather" <erather@forth.com> - 2017-01-13 15:08 -1000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-13 17:21 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-14 11:26 +0000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-13 18:21 -0800
Re: "Hello world" using Hughs novice package Paul Rubin <no.email@nospam.invalid> - 2017-01-13 18:30 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-13 22:20 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-14 10:43 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-14 15:47 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-14 17:30 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-14 18:16 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-15 13:53 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-15 14:09 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-15 15:48 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-15 16:00 -0800
Re: "Hello world" using Hughs novice package albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-01-15 12:48 +0100
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-14 10:10 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-15 17:56 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-15 17:05 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-15 17:35 -0800
Re: "Hello world" using Hughs novice package Paul Rubin <no.email@nospam.invalid> - 2017-01-15 19:20 -0800
Re: "Hello world" using Hughs novice package Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-01-15 23:51 -0500
Re: "Hello world" using Hughs novice package "Elizabeth D. Rather" <erather@forth.com> - 2017-01-15 19:22 -1000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-18 16:24 -0800
Re: "Hello world" using Hughs novice package foxaudioresearch@gmail.com - 2017-01-18 18:40 -0800
Re: "Hello world" using Hughs novice package Ron Aaron <rambamist@gmail.com> - 2017-01-19 06:46 +0200
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-18 23:25 -0800
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-19 09:47 +0000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-19 02:44 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-19 06:16 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-19 07:43 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-19 11:07 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-19 14:58 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-20 03:48 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-20 06:54 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-20 09:11 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-20 07:30 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-20 12:12 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-20 16:27 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-21 03:24 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-22 12:47 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-22 14:41 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-22 15:57 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-23 04:05 -0600
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-23 10:47 -0800
Re: "Hello world" using Hughs novice package Mark Wills <markwills1970@gmail.com> - 2017-01-24 01:02 -0800
Re: "Hello world" using Hughs novice package Paul Rubin <no.email@nospam.invalid> - 2017-01-24 01:12 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-23 16:28 -0800
Re: "Hello world" using Hughs novice package Mark Wills <markwills1970@gmail.com> - 2017-01-24 01:06 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-24 03:22 -0600
Re: "Hello world" using Hughs novice package albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-01-24 14:19 +0100
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-24 03:13 -0600
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-24 08:08 -0500
Re: "Hello world" using Hughs novice package albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-01-24 14:23 +0100
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-24 09:10 -0500
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-24 15:35 +0000
Persitent memory (was Re: "Hello world" using Hughs novice package) Alex <alex@rivadpm.com> - 2017-01-24 14:19 -0500
Re: Persitent memory (was Re: "Hello world" using Hughs novice package) Alex <alex@rivadpm.com> - 2017-01-24 15:00 -0500
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-24 14:49 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-25 03:26 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-26 04:27 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-26 08:35 -0600
Re: "Hello world" using Hughs novice package albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-01-21 14:19 +0100
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-22 12:55 -0800
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-19 15:28 +0000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-19 14:44 -0800
Re: "Hello world" using Hughs novice package Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-01-19 20:30 -0500
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-20 18:21 +0000
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-20 03:52 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-20 06:58 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-20 12:57 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-20 16:31 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-20 17:31 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-19 08:48 -0800
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-19 17:18 +0000
Re: "Hello world" using Hughs novice package alex@rivadpm.com - 2017-01-19 11:01 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-19 14:51 -0800
Re: "Hello world" using Hughs novice package albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-01-19 13:07 +0100
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-19 14:26 +0000
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-16 09:03 -0600
Re: "Hello world" using Hughs novice package "Elizabeth D. Rather" <erather@forth.com> - 2017-01-15 15:08 -1000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-15 17:23 -0800
Re: "Hello world" using Hughs novice package Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-01-15 22:18 -0500
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-16 09:08 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-18 06:56 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-14 09:31 +0000
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-15 17:33 -0600
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-10 09:55 +0000
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-09 04:05 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-09 16:00 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-10 04:13 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-12 06:40 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-02 21:07 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-03 04:46 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-03 16:11 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-04 04:27 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-04 14:26 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-04 23:09 +0000
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-05 00:02 +0000
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-05 02:19 -0800
Re: "Hello world" using Hughs novice package rickman <gnuarm@gmail.com> - 2017-01-05 05:56 -0500
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-05 06:33 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2017-01-05 16:56 +0100
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-05 19:03 +0000
Re: "Hello world" using Hughs novice package rickman <gnuarm@gmail.com> - 2017-01-06 06:45 -0500
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-05 04:27 -0600
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-05 06:22 -0800
Re: "Hello world" using Hughs novice package Andrew Haley <andrew29@littlepinkcloud.invalid> - 2017-01-05 09:10 -0600
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-04 23:05 +0000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-03 22:05 -0800
Re: "Hello world" using Hughs novice package Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-01-04 13:44 -0800
Re: "Hello world" using Hughs novice package "Elizabeth D. Rather" <erather@forth.com> - 2017-01-01 20:53 -1000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-01 19:55 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-01 21:13 -0800
Re: "Hello world" using Hughs novice package foxaudioresearch@gmail.com - 2017-01-02 07:14 -0800
Re: "Hello world" using Hughs novice package "Elizabeth D. Rather" <erather@forth.com> - 2017-01-02 07:42 -1000
Re: "Hello world" using Hughs novice package albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-01-03 02:00 +0100
Re: "Hello world" using Hughs novice package Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-01-03 00:13 -0500
Re: "Hello world" using Hughs novice package "Elizabeth D. Rather" <erather@forth.com> - 2017-01-02 22:02 -1000
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-03 11:19 +0000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-03 21:37 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-02 21:55 -0800
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-03 11:26 +0000
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-02 10:47 +0000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-02 20:57 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-30 18:35 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2016-12-31 04:29 +0100
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2016-12-31 10:19 +0000
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-02 17:08 +0000
Re: "Hello world" using Hughs novice package "HAA" <someone@microsoft.com> - 2017-01-06 13:39 +1100
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-05 19:13 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-27 23:57 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2016-12-30 20:54 +0100
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-29 19:05 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-29 19:38 -0800
Re: "Hello world" using Hughs novice package "HAA" <someone@microsoft.com> - 2016-12-30 15:24 +1100
Re: "Hello world" using Hughs novice package Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2016-12-30 16:01 +0000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-30 14:33 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-29 16:04 -0800
Re: "Hello world" using Hughs novice package "HAA" <someone@microsoft.com> - 2016-12-30 12:42 +1100
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2016-12-30 07:24 +0000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-30 12:50 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2016-12-30 21:43 +0000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-30 14:38 -0800
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2016-12-31 10:31 +0000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-31 07:04 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-31 07:07 -0800
Re: "Hello world" using Hughs novice package Julian Fondren <julian.fondren@gmail.com> - 2016-12-31 07:46 -0800
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2016-12-31 08:28 -0800
Re: "Hello world" using Hughs novice package albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2016-12-30 16:53 +0100
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-06 20:49 -0800
Re: "Hello world" using Hughs novice package Cecil Bayona <cbayona@cbayona.com> - 2017-01-06 23:28 -0600
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-06 22:22 -0800
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2017-01-07 14:55 +0100
Re: "Hello world" using Hughs novice package Alex <alex@rivadpm.com> - 2017-01-07 21:20 +0000
Re: "Hello world" using Hughs novice package awegel@arcor.de (Alexander Wegel) - 2017-01-07 22:57 +0100
Re: "Hello world" using Hughs novice package anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2017-01-08 17:02 +0000
Re: "Hello world" using Hughs novice package hughaguilar96@gmail.com - 2017-01-08 16:55 -0800
Page 13 of 14 — ← Prev page 1 … 11 12 [13] 14 Next page →
| From | awegel@arcor.de (Alexander Wegel) |
|---|---|
| Date | 2016-12-30 20:54 +0100 |
| Message-ID | <1myze6m.1xo4dhw1svampoN%awegel@arcor.de> |
| In reply to | #53578 |
<hughaguilar96@gmail.com> wrote: > > Now go fix your crappage, i'm (not) waiting for more than half a decade > > now (remember "alien alphabet"? your packages inflexibility kept you > > from solving it - LOL). > > This is a reference to this thread: > https://groups.google.com/forum/#!searchin/comp.lang.forth /Codejam%7Csort:relevance/comp.lang.forth/3Y4w_MdYl0k/kV-Cy3lwxMMJ > > I used my SEQ lists in my first solution. This worked for some of the > versions of the problem, but didn't work for others > because the SEQ strings are limited to 255 chars (I posted the code > without testing it on all versions of the problem, so I didn't realize > that some of the latter versions had strings over 255 chars). There were only two versions - a small and a big one: you are a dishonest person. > I then implemented SSEQ lists in LIST.4TH that allowed unlimited sized > strings, So, you had to implement a new datatype because the ones built into your package couldn't be adapted. > and rewrote my program to use SSEQ rather than SEQ --- that worked for all > versions of the problem. You said that my package's inflexibility kept me > from solving the problem --- that is not true --- you are a very dishonest > person! Wow - kudos from the master! OK, the packages shortcomings didn't completely stop you, but they did keep you from solving the full problem in time, and i fathom that without cut & paste programming, it would have taken you even longer. BTW: The SSEQ type is still not in the package (as it is publicized), so technically, the package is still not usable for your alien-language solution, (and we have to trust your word that you *really* implemented SSEQ, or did i miss sth?). > Anyway, I don't think it is fair to criticize me because my SEQ used > #1 and this was limited to 255 char strings --- I didn't invent > ANS-Forth with its complicated and feature-bereft string support > --- why not criticize the person who is guilty of pinching this loaf? I criticize you because it's you who claims he can do this and that, then doesn't deliver because he missed something (which is always someone elses fault) or skimped somewhere. > This was Alex Wegel's solution to the "alien alphabet" CodeJAM problem: > > On Tuesday, May 1, 2012 at 5:29:10 PM UTC-7, Alex Wegel wrote: > > <..x.nl> wrote: > > > > > awe..cor.de (Alex Wegel) writes Re: Google CodeJam? > > > > > > > As i said, it's another ugly solution - my "philosophy" was to leave > > > > everything out that wasn't really needed for the question. (This way, > > > > there's also less space for bugs to hide.) > > > > > > > I didn't put comments into the code (quel surprise!), but the basic > > > > concept is: The alien digits are already ordered (1,0,2,3,4,5,...), so > > > > it's easy to build a table for translating them. After the table has > > > > been built, the alien number-base is known, and i can feed the > > > > transliterated alien numeral to forth to get the numerical value. > > > > > > So why not add the above small explanation and some stack comments > > > to your code? I almost suspect that you deliberately deleted them :-) > > > > Actually i think i had 2 of them at some point in time, but that was > > about it, and then they went stale. They not so interesting anyway :-) > > See: > > > > #! /usr/local/bin/gforth-fast > > 0 value hi \ highest digit-value found so far > > create d 36 allot \ digit string containing all alien digits > > : wipe ( ) d 36 erase 0 to hi ; \ housekeeping > > : +dig ( c) d hi + c! 1 hi + to hi ; \ add newly learned digit to d > > : >dig? ( c -- +n true|c false) \ lookup alien digit > > hi begin dup while > > 1 - 2dup d + c@ = if nip true exit then > > repeat drop false ; > > : twiddle ( ca) dup >r c@ r@ char+ c@ r@ c! r> char+ c! ; \ exch 2 bytes > > : pars ( ca u) \ read alien numeral to determine digits & number base > > bounds do > > i c@ >dig? if drop else +dig then > > loop d twiddle hi 2 max to hi ; > > : dig> (+n--c) dup 9 > if 7 + then [char] 0 + ; \ convert 1 dig to text > > : eval ( ca u) \ evaluate alien number string > > 2dup pars 2dup bounds do i c@ >dig? drop dig> i c! loop > > hi base ! s>unumber? drop decimal ; > > : getl pad dup 64 stdin read-line throw drop ; > > : .. ." Case #" 1 .r ." : " 1 ud.r cr ; > > : app getl evaluate 0 do getl eval i 1+ .. wipe loop ; > > ' noop is bootmessage > > app bye > > > > Main thing to remember when reading the source is that in bottom up > > programming, the top is down. > > Note that I didn't modify this code to make it obfuscated Me either. You threatened to include it in your package, so i dropped the idea of producing a hugh-legible version. > (the way that he modified my EXCHANGE function to make it obfuscated). Next thing you write is that i peed in your pants. Dishonest moron. > I showed this code exactly as he wrote it. I appreciate this. > I said this: > > On Tuesday, May 1, 2012 at 8:45:08 PM UTC-7, Hugh Aguilar wrote: > > Your "plain Forth" would more accurately be called "obfuscated Forth" > > --- I've never written that in my life --- and I never will. > > > > I don't think that I could write a Forth program without stack-picture > > comments, as I would confuse myself. I think that you used stack- > > picture comments just like everybody else when you wrote your program, > > but then removed them afterward to obfuscate your code. So - i hope you see the stack picture comments. Can you read it now?
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2016-12-29 19:05 -0800 |
| Message-ID | <4e699477-ae4b-4ba8-9283-ff95c782b414@googlegroups.com> |
| In reply to | #53555 |
On Thursday, December 29, 2016 at 6:42:05 PM UTC-7, HAA wrote: > hughaguilar96@gmail.com wrote: > > > ... > > > I don't have the patience to write another STR>NUM function that is compatible with > > > the bizarre numeric conventions of ANS-Forth --- using the '.' to indicate a > > > double-precision integer is just bizarre --- an 'e' without a number after it is also > > > bizarre. > > > > > > There are very few people on comp.lang.forth who are capable of writing a STR>NUM > > > function. I will leave this as a New Year's challenge though --- if anybody does > > > this, and it works with the bizarre numeric conventions of the ANS-Forth > > > outer-interpreter, I will use it in MACRO: rather than my current STR>NUM that uses > > > my own numeric conventions. > > Anyone who has written their own forth can do this but it won't be a one-liner as it > represents a major part of INTERPRET. If you define NUMBER? and assume > >FLOAT then you should be half-way there. Would I want to duplicate what the > forth interpreter already does? Probably not, but then it's not my project. There are two ways to write a cross-compiler: 1.) Use the built-in outer-interpreter. 2.) Write your own outer-interpreter. In ANS-Forth: #1 doesn't work because LITERAL is not vectored so you can't have literal numbers in your TARG code --- you have to explicitly use LITERAL (and it will be your own LITERAL not the built-in LITERAL that the outer-interpreter uses) --- this is doable (I did this in MFX) but it results in ugly code that isn't really Forth at all. #2 doesn't work because FIND is broken (but my disambiguifiers fix this) and because there is no STR>NUM function exposed to the programmer (but I've written one now). Also, #2 doesn't work very well because QUIT is not vectored, so every time you get an abort you end up in the built-in outer-interpreter rather than in your own outer-interpreter. #1 is a lot easier than #1, with much less work required. I think that the ANS-Forth committee refused to make LITERAL vectored for the purpose of sabotaging cross-compiler writers. I notice that VFX has a lot of vectored words, but LITERAL isn't one of them. Stephen Pelc is trying to prevent people from using VFX to write cross-compilers --- he did vector QUIT though, so #2 is possible in VFX, although this is a lot more work than #1 --- I have actually done a lot of the work already though, by writing STR>NUM and making it publicly available.
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2016-12-29 19:38 -0800 |
| Message-ID | <86623c20-b403-4050-899c-c932ddec78cd@googlegroups.com> |
| In reply to | #53589 |
On Thursday, December 29, 2016 at 8:05:28 PM UTC-7, hughag...@gmail.com wrote: > #1 is a lot easier than #1, with much less work required. Typo --- I meant: #1 is a lot easier than #2, with much less work required.
[toc] | [prev] | [next] | [standalone]
| From | "HAA" <someone@microsoft.com> |
|---|---|
| Date | 2016-12-30 15:24 +1100 |
| Message-ID | <o44nh9$pr3$1@gioia.aioe.org> |
| In reply to | #53589 |
hughaguilar96@gmail.com wrote:
> On Thursday, December 29, 2016 at 6:42:05 PM UTC-7, HAA wrote:
> > hughaguilar96@gmail.com wrote:
> > > > ...
> > > > I don't have the patience to write another STR>NUM function that is compatible
> > > > with the bizarre numeric conventions of ANS-Forth --- using the '.' to indicate a
> > > > double-precision integer is just bizarre --- an 'e' without a number after it is
> > > > also bizarre.
> > > >
> > > > There are very few people on comp.lang.forth who are capable of writing a STR>NUM
> > > > function. I will leave this as a New Year's challenge though --- if anybody does
> > > > this, and it works with the bizarre numeric conventions of the ANS-Forth
> > > > outer-interpreter, I will use it in MACRO: rather than my current STR>NUM that
> > > > uses my own numeric conventions.
> >
> > Anyone who has written their own forth can do this but it won't be a one-liner as it
> > represents a major part of INTERPRET. If you define NUMBER? and assume
> > >FLOAT then you should be half-way there. Would I want to duplicate what the
> > forth interpreter already does? Probably not, but then it's not my project.
>
> There are two ways to write a cross-compiler:
> 1.) Use the built-in outer-interpreter.
> 2.) Write your own outer-interpreter.
>
> In ANS-Forth:
>
> #1 doesn't work because LITERAL is not vectored so you can't have literal numbers in
> your TARG code --- you have to explicitly use LITERAL (and it will be your own LITERAL
> not the built-in LITERAL that the outer-interpreter uses) --- this is doable (I did
> this in MFX) but it results in ugly code that isn't really Forth at all.
>
> #2 doesn't work because FIND is broken (but my disambiguifiers fix this) and because
> there is no STR>NUM function exposed to the programmer (but I've written one now).
> Also, #2 doesn't work very well because QUIT is not vectored, so every time you get an
> abort you end up in the built-in outer-interpreter rather than in your own
> outer-interpreter.
>
> #1 is a lot easier than #1, with much less work required. I think that the ANS-Forth
> committee refused to make LITERAL vectored for the purpose of sabotaging cross-compiler
> writers. I notice that VFX has a lot of vectored words, but LITERAL isn't one of them.
> Stephen Pelc is trying to prevent people from using VFX to write cross-compilers --- he
> did vector QUIT though, so #2 is possible in VFX, although this is a lot more work than
> #1 --- I have actually done a lot of the work already though, by writing STR>NUM and
> making it publicly available.
Perhaps because I tend to write straight apps and/or can hack my own compiler as
required, I don't run into these issues. Since you made STR>NUM a New Year's
challenge (!) I'll start the ball rolling. Not sure what is the spec for STR>NUM and
took a guess based on a previous post.
\ cut/paste from public domain code. needs testing. use at own risk
forth definitions decimal
0 dup constant #invalid
1+ dup constant #single
1+ dup constant #double
1+ constant #float
( user) variable dpl
\ trailing decimal pt sets DPL=0
: number? ( c-addr u -- d true | false )
over c@ [char] - = over 0> and dup >r
1 and /string over c@ [char] . > and
0 0 2swap ?dup if
>number -1 dpl ! dup if
1- over c@ [char] . - or 0 dpl !
then
while then
r> 2drop 2drop false
else
drop r> if dnegate then true
then ;
: escan ( c-addr u1 -- u2 ) \ 'E' or 'e'
begin dup while over c@ 32 or [char] e -
while 1 /string repeat then nip ;
: STR>NUM ( c-addr u -- number code | false )
\ base @ >r over c@ case
\ [char] % of binary 1 endof
\ [char] $ of hex 1 endof
\ [char] # of decimal 1 endof
\ 0 swap
\ endcase /string
2dup number? if
2nip dpl @ 0< if drop #single else #double then
else
2dup escan base @ 10 = and if
>float dup if drop #float then
else 2drop 0 then
then
\ r> base !
;
\\ testing
: t ( "string" )
bl word count ." >>> " str>num case
#invalid of ." not a number" endof
#single of ." single integer " . endof
#double of ." double integer " d. endof
#float of ." float " fs. endof
1 abort" should never get here!"
endcase ;
[toc] | [prev] | [next] | [standalone]
| From | Gerry Jackson <gerry@jackson9000.fsnet.co.uk> |
|---|---|
| Date | 2016-12-30 16:01 +0000 |
| Message-ID | <o460ae$oca$1@dont-email.me> |
| In reply to | #53589 |
On 30/12/2016 03:05, hughaguilar96@gmail.com wrote:
> There are two ways to write a cross-compiler:
> 1.) Use the built-in outer-interpreter.
> 2.) Write your own outer-interpreter.
>
> In ANS-Forth:
>
> #1 doesn't work because LITERAL is not vectored so you can't have
> literal numbers in your TARG code --- you have to explicitly use
> LITERAL (and it will be your own LITERAL not the built-in LITERAL
> that the outer-interpreter uses) --- this is doable (I did this in
> MFX) but it results in ugly code that isn't really Forth at all.
Aren't you contradicting yourself by saying "this is doable" by using
something like [ 1234 ] LITERAL inside a colon definition. If that is
true, and it is, then #1 does work. The fact that it is ugly code is
irrelevant - it is ANS Forth and works.
>
> #2 doesn't work because FIND is broken (but my disambiguifiers fix
> this) and because there is no STR>NUM function exposed to the
> programmer (but I've written one now).
So #2 can work because you have provided a way for it to work, people
can use your solution - problem resolved - the world should thank you, I
would but I went for method #1.
> Also, #2 doesn't work very
> well because QUIT is not vectored, so every time you get an abort
> you end up in the built-in outer-interpreter rather than in your
> own outer-interpreter.
>
Two things
1. When cross compiling, if something fails why would you want to stay
in the custom outer interpreter (I've asked this before and never
received a reply)?
2. In the cross compiler when an error occurs use ABORT or ABORT" or
THROW so that an exception is thrown and do something like this to stay
in my-outer-interpreter:
: some-action-that-may-fail
...
some-error? if abort ... then
...
;
: my-outer-interpreter
...
['] some-action-that-may-fail catch
?dup if ( an exception was thrown )
( so do whatever recovery you can )
then
...
;
--
Gerry
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2016-12-30 14:33 -0800 |
| Message-ID | <0af5111a-d299-488b-bc47-8e19f4244dc0@googlegroups.com> |
| In reply to | #53611 |
On Friday, December 30, 2016 at 9:01:45 AM UTC-7, Gerry wrote: > On 30/12/2016 03:05, hughaguilar96@gmail.com wrote: > > There are two ways to write a cross-compiler: > > 1.) Use the built-in outer-interpreter. > > 2.) Write your own outer-interpreter. > > > > In ANS-Forth: > > > > #1 doesn't work because LITERAL is not vectored so you can't have > > literal numbers in your TARG code --- you have to explicitly use > > LITERAL (and it will be your own LITERAL not the built-in LITERAL > > that the outer-interpreter uses) --- this is doable (I did this in > > MFX) but it results in ugly code that isn't really Forth at all. > > Aren't you contradicting yourself by saying "this is doable" by using > something like [ 1234 ] LITERAL inside a colon definition. If that is > true, and it is, then #1 does work. The fact that it is ugly code is > irrelevant - it is ANS Forth and works. What??? You can't write a cross-compiler in ANS-Forth that cross-compiles ANS-Forth code. These are both examples of ANS-Forth functions: : testA 1234 + ; : testB [ 1234 ] literal + ; The cross-compiler isn't going to be able to cross-compile testA --- the cross-compiler has failed to cross-compile a simple Forth function. Using code like testB is "doable" but it requires the user to write his code in an ugly and restrictive manner. If the user has existing ANS-Forth code that he wants to cross-compile, he will have to manually modify it to conform to the pointless restriction of not having any literal numbers. This is extremely unprofessional! If you tell the user that he can't have literal numbers in his source-code, he will likely say: "Why not? I can cross-compile C programs that have literal numbers in the source-code. You Forth programmers are clowns --- you struggle with basic concepts such as literal integers --- I will just go back to programming in C again." When I wrote MFX at Testra, I told them about the restriction of not having literal numbers, and they didn't fire me. They just said that they would put up with the hassle. They were primarily focused on getting their motion-control program ported over to the MiniForth, and they were willing to manually modify the source-code as necessary to conform to the the cross-compiler's restrictions. AFAIK, the motion-control program is the only program that has ever been written in MFX. Also, AFAIK, nobody outside of Testra has ever programmed in MFX. If your cross-compiler is going to be purely in-house, then "doable" is good enough --- this is not commercial quality however. Straight Forth isn't going to be exactly compatible with any micro-controller Forth that is being cross-compiled. It is going to be reasonably close though. Simple functions such as this should compile under either: : testA 1234 + ; These won't compile under the micro-controller cross-compiler though: : testC 5/9 * ; : testD 3.1415926535897932385 * ; Both of these functions will have to be manually modified to use */ instead. Here is one that won't work because it is a single precision integer in Straight Forth (which is 64-bit) but would need to be a double precision integer in any micro-controller Forth (presumably 32-bit): : testE 5,000,000,000 + ; > > #2 doesn't work because FIND is broken (but my disambiguifiers fix > > this) and because there is no STR>NUM function exposed to the > > programmer (but I've written one now). Anton Ertl told me how to write disambiguifiers back in 2009. It wasn't until years later when I discovered them on my own and remembered that I had been told about them before, that I also realized that disambiguifiers are the key to solving quite a lot of problems in ANS-Forth. The good news is that ANS-Forth is not as badly screwed up as I had previously believed (having FIND broken is pretty badly screwed up) --- the broken FIND can be fixed with disambiguifiers. Ironically however, the committee members (Anton Ertl, Bernd Paysan and Stephen Pelc) now refuse to acknowledge the existence of the disambiguifiers --- accepting the disambiguifiers requires them to admit that ANS-Forth is ambiguous --- this is a common human failing: to become over-attached to some technology and then refuse to admit that it has problems, even to the point of refusing to fix the problems when a solution is known. > So #2 can work because you have provided a way for it to work, people > can use your solution - problem resolved - the world should thank you, I > would but I went for method #1. > > > Also, #2 doesn't work very > > well because QUIT is not vectored, so every time you get an abort > > you end up in the built-in outer-interpreter rather than in your > > own outer-interpreter. > > Two things > 1. When cross compiling, if something fails why would you want to stay > in the custom outer interpreter (I've asked this before and never > received a reply)? I don't recall you asking this before. It seems obvious though. Switching back and forth between two outer-interpreters would be very confusing. The user is going to end up back in the built-in outer-interpreter and then the cross-compiler is no longer working and he wonders why, then he realizes that he has to manually get back into the correct outer-interpreter so that things will start working again. Ugh! Unprofessional! > 2. In the cross compiler when an error occurs use ABORT or ABORT" or > THROW so that an exception is thrown and do something like this to stay > in my-outer-interpreter: > > : some-action-that-may-fail > ... > some-error? if abort ... then > ... > ; > > : my-outer-interpreter > ... > ['] some-action-that-may-fail catch > ?dup if ( an exception was thrown ) > ( so do whatever recovery you can ) > then > ... > ; Certainly, if you are going to manually use ABORT or ABORT" or THROW then these will be your own that you wrote yourself and which go back to your own outer-interpreter. Isn't it true though, that there are built-in functions that use ABORT or ABORT" or THROW internally? These are going to go back to the built-in outer-interpreter I think #2 will work. Even though QUIT isn't vectored, this may not matter (it would only matter if built-in words can abort). So, for the most part, #2 is the only solution that will work. The problem though is that writing your own cross-compiler is a lot of work. The amount of work involved here is comparable to the amount of work involved in writing your own Forth system from scratch. The outer-interpreter is the heart of any Forth system, so writing it yourself is pretty much the same as writing your own Forth system entirely. Solution #1, using the built-in outer-interpreter, is much much easier! This is pretty easy. I did this at Testra. If I had told them that I needed to write my own outer-interpreter, they would have likely balked, because they didn't have the time or the money for such a large project. Using the built-in outer-interpreter is significantly simpler and is the obvious solution. ANS-Forth however, is crippled because LITERAL is not vectored, which prevents the built-in outer-interpreter from being used (except in the ugly hacky way described above) --- ANS-Forth was purposely crippled to make the built-in outer-interpreter unusable for cross-compilers --- Elizabeth Rather sabotaged both Forth-83 and ANS-Forth to prevent common Forth programmers from writing cross-compilers in competition with Forth Inc..
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2016-12-29 16:04 -0800 |
| Message-ID | <69587433-ba0a-4ae3-9ed6-ecb414e14705@googlegroups.com> |
| In reply to | #53555 |
On Monday, December 26, 2016 at 7:16:29 PM UTC-7, hughag...@gmail.com wrote:
> There are some complications:
> ...
> 2.) I used STR>NUM to convert strings to numbers in MACRO: --- this works, but it is not compatible with the ANS-Forth outer-interpreter. For example, a float such as 2e is illegal for STR>NUM and has to be converted to 2. or 2.e1 which are both legal. A double such as 2. would be interpreted as a float by STR>NUM and has to be converted to ,2 which is legal.
> ...
> The biggest problem with my new-and-improved MACRO: is that it uses STR>NUM which isn't compatible with the ANS-Forth outer-interpreter string-to-number conversion code (which weirdly isn't exposed to the ANS-Forth user). Some literal numbers may need to be modified to work with STR>NUM rules --- this is only an issue for doubles and floats.
>
> I don't have the patience to write another STR>NUM function that is compatible with the bizarre numeric conventions of ANS-Forth --- using the '.' to indicate a double-precision integer is just bizarre --- an 'e' without a number after it is also bizarre.
>
> There are very few people on comp.lang.forth who are capable of writing a STR>NUM function. I will leave this as a New Year's challenge though --- if anybody does this, and it works with the bizarre numeric conventions of the ANS-Forth outer-interpreter, I will use it in MACRO: rather than my current STR>NUM that uses my own numeric conventions.
As an example of this, in the novice-package I had this:
macro: ftanh ( -- ) \ float: n -- tanh(n)
f2* fexpm1 fdup 2e f+ f/ ;
When I compiled I got this:
FTANH is redefined *** MACRO: didn't recognize the string ***
Source: "novice.4th" on line 2596
-> f2* fexpm1 fdup 2e f+ f/ ;
^
So I changed to this:
macro: ftanh ( -- ) \ float: n -- tanh(n)
f2* fexpm1 fdup 2e1 f+ f/ ;
This worked. I could have also done this, which also works:
macro: ftanh ( -- ) \ float: n -- tanh(n)
f2* fexpm1 fdup 2. f+ f/ ;
It is a hassle to make these changes. Also, if I convert FTANH from a MACRO: to a : definition later, it won't work under the ANS-Forth outer-interpreter, and will have to be changed back again.
I think that I will upgrade STR>NUM so that it will accept a float with an 'e' but with no exponent (it will just assume a 1 as the exponent if the exponent is missing). I think this is a goofy numeric convention --- nobody else in the world does this --- it is obviously just a kludge to allow the '.' to continue to be used to indicate a double-precision integer.
I hate wasting time writing ANS-Forth code, but I'm already this far, so I might as well continue. This will allow macros to have float constants and be compatible between STR>NUM (used in the MACRO: definer) and ANS-Forth's code used in the outer-interpreter. It will still be necessary to change any double-precision integer constants though --- STR>NUM allows commas anywhere throughout, but assumes that a comma at the front indicates double-precision
I'm not aware of any ANS-Forth compiler that is actually in compliance with ANS-Forth in regard to double-precision constants. This is what the ANS-Forth document says:
---------------------------------------------------------------------------
3.4.1.3 Text interpreter input number conversion
When converting input numbers, the text interpreter shall recognize both
positive and negative numbers, with a negative number represented by a
single minus sign, the character “-”, preceding the digits. The
value in BASE is the radix for number conversion.
---------------------------------------------------------------------------
Also, we have this:
---------------------------------------------------------------------------
8.3.2 Text interpreter input number conversion
When the text interpreter processes a number that is immediately followed by
a decimal point and is not found as a definition name, the text interpreter
shall convert it to a double-cell number.
For example, entering DECIMAL 1234 leaves the single-cell number 1234 on the stack,
and entering DECIMAL 1234. leaves the double-cell number 1234 0 on the stack.
See: 3.4.1.3 Text interpreter input number conversion.
---------------------------------------------------------------------------
The document clearly states that only a '.' immediately after a number indicates that the number is double-precision. SwiftForth allows either a '.' or a ',' or a ':' anywhere in the number to indicated that it is double-precision. VFX is the same except doesn't allow the ':' at all. I just figured this out from experimentation --- there may be other weird ways to indicate a double-precision constant --- maybe this is documented in the
compilers' own manuals, but I didn't bother to RTFM because I don't really care.
ANS-Forth is the standard where "anything is possible" --- an ANS-Forth compiler can do pretty much anything, in contradiction with other ANS-Forth compilers, and programs won't port --- but so long as the compiler-writer brown-noses Elizabeth Rather, then his compiler gets to be declared to be ANS-Forth compliant.
As a practical matter, I don't actually have any macros that have double-precision integer literal values --- this may be rare for everybody --- macros with float literal values are quite common however.
Anyway, the next novice-package release will be in a few days --- if anybody wants a copy now for testing, I will email it --- I want it tested thoroughly before I release it.
[toc] | [prev] | [next] | [standalone]
| From | "HAA" <someone@microsoft.com> |
|---|---|
| Date | 2016-12-30 12:42 +1100 |
| Message-ID | <o44e18$gcj$1@gioia.aioe.org> |
| In reply to | #53592 |
hughaguilar96@gmail.com wrote: > > ... > > I don't have the patience to write another STR>NUM function that is compatible with > > the bizarre numeric conventions of ANS-Forth --- using the '.' to indicate a > > double-precision integer is just bizarre --- an 'e' without a number after it is also > > bizarre. > > > > There are very few people on comp.lang.forth who are capable of writing a STR>NUM > > function. I will leave this as a New Year's challenge though --- if anybody does > > this, and it works with the bizarre numeric conventions of the ANS-Forth > > outer-interpreter, I will use it in MACRO: rather than my current STR>NUM that uses > > my own numeric conventions. Anyone who has written their own forth can do this but it won't be a one-liner as it represents a major part of INTERPRET. If you define NUMBER? and assume >FLOAT then you should be half-way there. Would I want to duplicate what the forth interpreter already does? Probably not, but then it's not my project.
[toc] | [prev] | [next] | [standalone]
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2016-12-30 07:24 +0000 |
| Message-ID | <2016Dec30.082404@mips.complang.tuwien.ac.at> |
| In reply to | #53592 |
hughaguilar96@gmail.com writes:
>macro: ftanh ( -- ) \ float: n -- tanh(n)
> f2* fexpm1 fdup 2e f+ f/ ;
>
>When I compiled I got this:
>
>FTANH is redefined *** MACRO: didn't recognize the string ***
> Source: "novice.4th" on line 2596=20
> -> f2* fexpm1 fdup 2e f+ f/ ;
> ^
>
>So I changed to this:
>
>macro: ftanh ( -- ) \ float: n -- tanh(n)
> f2* fexpm1 fdup 2e1 f+ f/ ;
2e f. 2. ok
2e1 f. 20. ok
- 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 | hughaguilar96@gmail.com |
|---|---|
| Date | 2016-12-30 12:50 -0800 |
| Message-ID | <01e349f1-e911-4e21-acdf-bf532b830754@googlegroups.com> |
| In reply to | #53606 |
On Friday, December 30, 2016 at 12:28:26 AM UTC-7, Anton Ertl wrote:
> hughaguilar96@gmail.com writes:
> >macro: ftanh ( -- ) \ float: n -- tanh(n)
> > f2* fexpm1 fdup 2e f+ f/ ;
> >
> >When I compiled I got this:
> >
> >FTANH is redefined *** MACRO: didn't recognize the string ***
> > Source: "novice.4th" on line 2596=20
> > -> f2* fexpm1 fdup 2e f+ f/ ;
> > ^
> >
> >So I changed to this:
> >
> >macro: ftanh ( -- ) \ float: n -- tanh(n)
> > f2* fexpm1 fdup 2e1 f+ f/ ;
>
> 2e f. 2. ok
> 2e1 f. 20. ok
Right! I realized that later.
Anyway, I upgraded STR>NUM so that it now accepts 2e as an equivalent to 2e0 (note that 3 is the code for a float, whereas 1 and 2 are codes for single and double integers, and 0 is a code for invalid):
s" 2e" str>num . 3 ok F:-1
f. 2. ok
s" 2e0" str>num . 3 ok F:-1
f. 2. ok
s" 2." str>num . 3 ok F:-1
f. 2. ok
The macros that contain floats have been changed back to how they were:
macro: ftanh ( -- ) \ float: n -- tanh(n)
f2* fexpm1 fdup 2e f+ f/ ;
All the macros can now be compiled with either the early-binding or late-binding version of MACRO: --- this is because none of them contain any double-precision integer literals --- doubles will still screw everything up.
As I said before though, none of the ANS-Forth compilers are compatible with each other in regard to how they handle doubles. The ANS-Forth standard says that a double is indicated by a '.' at the right end --- all of them ANS-Forth compilers accept various other indicators --- programs that contain double literals that use any indicator other than the '.' at the right are not going to be portable to other ANS-Forth compilers because this is non-standard vendor-specific code.
[toc] | [prev] | [next] | [standalone]
| From | Alex <alex@rivadpm.com> |
|---|---|
| Date | 2016-12-30 21:43 +0000 |
| Message-ID | <o46kbq$bdk$1@dont-email.me> |
| In reply to | #53621 |
On 12/30/2016 20:50, hughaguilar96@gmail.com wrote: > > As I said before though, none of the ANS-Forth compilers are > compatible with each other in regard to how they handle doubles. The > ANS-Forth standard says that a double is indicated by a '.' at the > right end --- all of them ANS-Forth compilers accept various other > indicators --- programs that contain double literals that use any > indicator other than the '.' at the right are not going to be > portable to other ANS-Forth compilers because this is non-standard > vendor-specific code. > You are wrong when you say they are incompatible with each other. They all recognise numbers with a '.' as the last character as a double. They are all compatible with the standard. You are right when you note other techniques are not portable because they're non-standard. That's because, to state the bleedin' obvious, the other techniques are not in the standard. -- Alex
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2016-12-30 14:38 -0800 |
| Message-ID | <4a97af9b-e0bd-4e0c-925b-6ed84ba6a5ec@googlegroups.com> |
| In reply to | #53623 |
On Friday, December 30, 2016 at 2:43:49 PM UTC-7, Alex wrote: > On 12/30/2016 20:50, hughaguilar96@gmail.com wrote: > > > > > As I said before though, none of the ANS-Forth compilers are > > compatible with each other in regard to how they handle doubles. The > > ANS-Forth standard says that a double is indicated by a '.' at the > > right end --- all of them ANS-Forth compilers accept various other > > indicators --- programs that contain double literals that use any > > indicator other than the '.' at the right are not going to be > > portable to other ANS-Forth compilers because this is non-standard > > vendor-specific code. > > > > You are wrong when you say they are incompatible with each other. They > all recognise numbers with a '.' as the last character as a double. They > are all compatible with the standard. > > You are right when you note other techniques are not portable because > they're non-standard. That's because, to state the bleedin' obvious, the > other techniques are not in the standard. BTW: How many ANS-Forth programmers know that this is not ANS-Forth? 2e The ANS-Forth Standard only allows 'E' to be used and not 'e' --- almost all ANS-Forth programs use literal floats with 'e' though --- so, none of them are actually ANS-Forth programs.
[toc] | [prev] | [next] | [standalone]
| From | Alex <alex@rivadpm.com> |
|---|---|
| Date | 2016-12-31 10:31 +0000 |
| Message-ID | <o481ah$qj2$1@dont-email.me> |
| In reply to | #53625 |
On 12/30/2016 22:38, hughaguilar96@gmail.com wrote:
>
> BTW: How many ANS-Forth programmers know that this is not ANS-Forth?
>
> 2e
>
> The ANS-Forth Standard only allows 'E' to be used and not 'e' ---
> almost all ANS-Forth programs use literal floats with 'e' though ---
> so, none of them are actually ANS-Forth programs.
>
Correct. But that's standards for you; don't follow them at your peril.
I'd support a change to the text interpreter to recognise { D | d | E |
e } as in >FLOAT. Would you like to propose this change?
--
Alex
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2016-12-31 07:04 -0800 |
| Message-ID | <cde67893-3fcc-419a-b9e5-1a1662f54680@googlegroups.com> |
| In reply to | #53639 |
On Saturday, December 31, 2016 at 3:31:09 AM UTC-7, Alex wrote:
> On 12/30/2016 22:38, hughaguilar96@gmail.com wrote:
>
> >
> > BTW: How many ANS-Forth programmers know that this is not ANS-Forth?
> >
> > 2e
> >
> > The ANS-Forth Standard only allows 'E' to be used and not 'e' ---
> > almost all ANS-Forth programs use literal floats with 'e' though ---
> > so, none of them are actually ANS-Forth programs.
> >
>
> Correct. But that's standards for you; don't follow them at your peril.
> I'd support a change to the text interpreter to recognise { D | d | E |
> e } as in >FLOAT. Would you like to propose this change?
>
>
> --
> Alex
How bizarre is this??? Alex McDonald is asking me if I want to propose a change --- write an RfD for Forth-200x --- this is despite the fact that I left Forth-200x and slammed the door behind me.
In this thread I wrote an early-binding version of MACRO: --- if I do say so myself, this is pretty awesome code --- this is comparable to my rquotations in awesomeness!
I enjoy writing Forth code and it is something that I take pride in. Elizabeth Rather hates me for this. She herself has never posted any code on comp.lang.forth that she didn't copy directly out of the "Starting Forth" book. The Forth-200x mailing list is full of people who, like her, never write Forth code and don't understand the concept of taking pride in code that they write themselves. They just want to be big Forth experts --- by writing RfDs and getting them accepted, they get to claim that they help to write the Standard --- they get to claim that mere Forth programmers such as myself are entirely dependent upon their genius for guidance.
The proposal that Alex McDonald is suggesting is trivial. Any Forth programmer with at least one week of experience could write this RfD. Also, the RfD is guaranteed to be accepted. Leon Wagner decides if an RfD is accepted or not, and these are his criteria:
1.) Implementing the code must take less than 10 minutes of his time.
2.) Documenting it must take only one or two sentences and should be understandable by anybody with one week of Forth experience.
3.) It must not have any affect whatsoever on existing SwiftForth code, or on possible future SwiftForth code that is written according to typical Forth Inc. style.
The proposal that Alex McDonald is suggesting that I put my name on, fits all of these criteria, so it is pretty much guaranteed to be accepted by Leon Wagner.
The only purpose of the Forth-200x mailing list is so Elizabeth Rather can collect names of Forth programmers and list them in the document as supporters. If I put my name on this proposal, then I have essentially sold my soul to Forth Inc.. I won't be able to complain when they list my name as a "contributor" because I did in fact contribute an RfD and got it accepted. The Forth-200x committee will have bought my soul and paid me essentially nothing --- they can spend the rest of forever telling the world that I am one of their little sycophants --- they will totally own me!
So, no, I'm not going to write a Forth-200x RfD for your proposal --- to sell my soul, I would want an infinitely higher price than you are offering --- at least one penny...
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2016-12-31 07:07 -0800 |
| Message-ID | <f780088f-a6b9-4f61-9ced-e37c4cbf32da@googlegroups.com> |
| In reply to | #53642 |
On Saturday, December 31, 2016 at 8:04:53 AM UTC-7, hughag...@gmail.com wrote:
> On Saturday, December 31, 2016 at 3:31:09 AM UTC-7, Alex wrote:
> > On 12/30/2016 22:38, hughaguilar96@gmail.com wrote:
> >
> > >
> > > BTW: How many ANS-Forth programmers know that this is not ANS-Forth?
> > >
> > > 2e
> > >
> > > The ANS-Forth Standard only allows 'E' to be used and not 'e' ---
> > > almost all ANS-Forth programs use literal floats with 'e' though ---
> > > so, none of them are actually ANS-Forth programs.
> > >
> >
> > Correct. But that's standards for you; don't follow them at your peril.
> > I'd support a change to the text interpreter to recognise { D | d | E |
> > e } as in >FLOAT. Would you like to propose this change?
> >
> >
> > --
> > Alex
>
> So, no, I'm not going to write a Forth-200x RfD for your proposal --- to sell my soul, I would want an infinitely higher price than you are offering --- at least one penny...
I forgot to mention --- this proposal is stupid anyway --- no language other than ANS-Forth uses 'd' or 'D' as an indicator for exponents. LOL
[toc] | [prev] | [next] | [standalone]
| From | Julian Fondren <julian.fondren@gmail.com> |
|---|---|
| Date | 2016-12-31 07:46 -0800 |
| Message-ID | <ee60eb57-ef02-4749-9de1-cfce9265bd26@googlegroups.com> |
| In reply to | #53639 |
On Saturday, December 31, 2016 at 4:31:09 AM UTC-6, Alex wrote: > On 12/30/2016 22:38, hughaguilar96@gmail.com wrote: > > > > > BTW: How many ANS-Forth programmers know that this is not ANS-Forth? > > > > 2e > > > > The ANS-Forth Standard only allows 'E' to be used and not 'e' --- > > almost all ANS-Forth programs use literal floats with 'e' though --- > > so, none of them are actually ANS-Forth programs. > > > > Correct. But that's standards for you; don't follow them at your peril. Rather, they're ANS Forth programs with an environmental dependency on lowercase 'e' being acceptable in that notation. This dependency is broadly satisfied in practice and would be easy to deal with when it isn't. Outside of Java, portability is not a binary condition but a statement about how much and what kind of effort it would take to port some software. I have plenty of substantial Perl written that depends on cPanel and CentOS which would need significant porting effort were it to need to run under Plesk, for example. The existence of ANS Forth *allows* descriptions of portability more professional and precise than "it works, right now, on these systems". If such descriptions seem scarce, so do professional Forth programmers. The only thing Hugh has added to clf in his entire time here is an awareness that CREATE ... DOES> with constant data is less optimal than could be. Possibly some people have also benefited by having been encouraged to get real Usenet clients or subscriptions--so as to avoid him. All of his other contributions have been negative. We are actually stupider because of him--people have stopped coming by, that brightened things up; people who know better don't bother voicing response #1929 to the same iterated complaint from Hugh that was stupid and baseless the first time it provoked a response. And of course, instead of Forth discussion, you get the occasional admissions like mine that moderators can be nice to have, that the problems they exhibit shouldn't be solved by doing away with them. At one point I would've defended to the death Hugh's right to fantasize grossly about people going to hell, as the saying goes, and now I would just shrug and say he had it coming were jack-booted thugs to black-bag him and remove him from society.
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2016-12-31 08:28 -0800 |
| Message-ID | <48929c0c-781d-446d-af0a-584131db6645@googlegroups.com> |
| In reply to | #53644 |
On Saturday, December 31, 2016 at 8:46:15 AM UTC-7, Julian Fondren wrote: > ...I would just shrug and say he had it coming were jack-booted > thugs to black-bag him and remove him from society. This isn't the first death threat that I've received. This was sent in private email: ----------------------------------------------------------------------------- On Wed, Jun 8, 2016 at 2:29 PM, Alex McDonald <alex@rivadpm.com> wrote: On 01/06/16 16:20, hughaguilar96@gmail.com wrote: > The RfD was going to be a slam-dunk from a ladder for Alex McDonald > --- but then Alex McDonald disappeared --- now the RfD is left in > limbo while Anton and Bernd search for a new pocket-boy who will put > his name on the RfD. Then the Forth-200x committee had Alex McDonald pretending to represent >the "Forth community," but Alex "I do standards for a living" McDonald > disappeared. This is a chronic problem for the Forth-200x committee > --- their pocket boys disappear --- then they have to find new > pocket boys to put their names on the RfDs. Unfortunately, you're still here, and I suspect you won't do me the tremendous favour of fucking off or dieing any time soon. Ah well. I still occasionally read clf. Personal reasons and your continued existence have stopped me being an active contributor. I'll continue to lurk for the moment. -- Alex "I still do standards for a living" McDonald ----------------------------------------------------------------------------- I think Forth-200x is essentially dead --- the Forth-200x committee have embraced Alex McDonald and Julien Fondren --- by doing this, they ruin their own reputation. I predict that everybody on the Forth-200x mailing list will opt out because they don't want to be involved in a cult anymore --- they don't want to associate with people who make death threats --- even by the low standards of the modern-day internet, death threats are still considered to be unacceptable. I also predict that the Forth-200x committee will continue to list their names on the Forth-200x document as "contributors" because they were on the mailing list at least for a while --- the Forth-200x document will be released with a long list of contributors and will appear to have full support from the Forth community to the casual observer --- the Forth-200x committee will spend the rest of forever braying about how they alone determine what Standard Forth is, and how the entire Forth community is fully supportive of them and entirely dependent upon them for leadership. I furthermore predict that the real world will totally ignore Forth-200x --- just like the real world has totally ignored ANS-Forth beginning in 1994 when it was released and continuing until today --- Elizabeth Rather attracts jerks like Alex McDonald and Julien Fondren, but decent folk avoid her like the plague. Well, tomorrow is New Years Day --- it is traditional to make predictions for the new year --- yet another prediction is that Stephen Pelc and his employee Peter Knaggs will both resign from the Forth-200x committee in 2017, and Elizabeth Rather will appoint one or more of the following to the Forth-200x committee in their place: Alex McDonald (if they can afford him; he does "do standards for a living") Julien Fondren (the second most likely candidate) Alex Wegel (the most likely candidate) Rickman (if he agrees to reveal his real name) John Passaniti (if they can find him)
[toc] | [prev] | [next] | [standalone]
| From | albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) |
|---|---|
| Date | 2016-12-30 16:53 +0100 |
| Message-ID | <o45vu8$ovu$1@cherry.spenarnc.xs4all.nl> |
| In reply to | #53555 |
In article <955f42cb-6a57-45d4-be90-cd31167e994c@googlegroups.com>,
<hughaguilar96@gmail.com> wrote:
>
>There are very few people on comp.lang.forth who are capable of writing a S=
>TR>NUM function. I will leave this as a New Year's challenge though --- if =
>anybody does this, and it works with the bizarre numeric conventions of the=
> ANS-Forth outer-interpreter, I will use it in MACRO: rather than my curren=
>t STR>NUM that uses my own numeric conventions.
My answer to that challenge is: "mu". As far as ciforth is concerned.
There is no good reason to stick to the Brodie picture of parting the
input string into words, that are then machined.
Instead I've a PARSE-INT that gets the characters directly from the input
stream. Note that we need such a mechanism anyway, otherwise we could not
handle strings with spaces, even if if the word that does that is followed
by a space.
I don't care about vectoring. In an indirect threaded Forth all words can be
vectored.
Adding floating point parsing in hindsight goes like this
(EPL is the place of the exponent sign).
This is to replace the old (NUMBER) by revectoring.
: (NUMBER) NULL EPL !
'PARSE-INT CATCH DUP
10 = IF \ Error 10 means : not a digit according to BASE.
PP @ 1- C@ XC = AND IF \ one char back, is it an exponent sign?
PP @ 1- EPL ! PARSE-FLOAT
( ELSE leave error code)
THEN
THEN THROW ;
Now PARSE-FLOAT parses backwards from the exponent sign, which is very
convenient. Any excess digits fall over the edge like so
repeat (leaving out detection of the decimal point)
parse one digit backwards
Add the digit to the fp number
Divide by 10
For the exponent it uses PARSE-INT again.
So bottom line: very modular. No STR>NUM in sight.
: SDFLITERAL
EPL @ IF POSTPONE FLITERAL EXIT THEN
DPL @ IF POSTPONE DLITERAL EXIT THEN
LITERAL ;
One remark: the only reason numbers are intertwined is that they all
start the same: with a digit.
In the Dutch Forth Chapter I meet a strong advocate of separate prefixes
like FX for floating point numbers. That has something going for it, but
will be hated by anyone thinking that Forth must mimic notations from
other languages.
Groetjes Albert
--
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 | hughaguilar96@gmail.com |
|---|---|
| Date | 2017-01-06 20:49 -0800 |
| Message-ID | <2d28d4f1-55e4-4c19-8df3-d26d18a879fb@googlegroups.com> |
| In reply to | #53555 |
On Monday, December 26, 2016 at 7:16:29 PM UTC-7, hughag...@gmail.com wrote:
> Now I have disambiguifiers in the novice-package (to be released in a few days). So, I rewrote MACRO: to use early-binding (note that LATE-MACRO: is the old late-binding MACRO: that I have been using all these years):
Included among the disambiguifiers are COMPILE, CS-PICK CS-ROLL --- I have now added these definitions after the disambiguifiers:
: compile, ( xt -- )
state @ 0= abort" *** COMPILE, was used in interpretive mode (typically a MACRO: caused this) ***"
compile, ;
: cs-pick ( u -- ) \ control: a b... -- a b... a
state @ 0= abort" *** CS-PICK was used in interpretive mode ***"
cs-pick ;
: cs-roll ( u -- ) \ control: a b... -- b... a
state @ 0= abort" *** CS-ROLL was used in interpretive mode ***"
cs-roll ;
These now become non-immediate, which makes more sense than being immediate --- the rest of the disambiguifiers should be immediate though, and are left as they are.
The advantage here is that I can POSTPONE COMPILE, in MACRO: and then, if the macro is used in interpretive mode, it will abort with a helpful error message. If I left the COMPILE, disambiguifier as it was, then it wouldn't abort like this (because the POSTPONE is being done at compile-time when STATE @ is non-zero) and what gets compiled by the POSTPONE doesn't check for STATE @ being zero like it should.
With this change, a macro that is used in interpretive mode will abort with an error message --- this wasn't happening before --- it just quietly compiled code into the dictionary, which makes no sense at all in interpretive mode.
I think I have ANS-Forth totally fixed now in regard to making FIND work correctly on everything and making words be either immediate or non-immediate in a way that makes sense --- the disambiguifiers upgrade ANS-Forth to the level of Forth-83 again!
[toc] | [prev] | [next] | [standalone]
| From | Cecil Bayona <cbayona@cbayona.com> |
|---|---|
| Date | 2017-01-06 23:28 -0600 |
| Message-ID | <o4pu67$fkj$1@dont-email.me> |
| In reply to | #53797 |
On 1/6/2017 10:49 PM, hughaguilar96@gmail.com wrote: > On Monday, December 26, 2016 at 7:16:29 PM UTC-7, hughag...@gmail.com wrote: >> Now I have disambiguifiers in the novice-package (to be released in a few days). So, I rewrote MACRO: to use early-binding (note that LATE-MACRO: is the old late-binding MACRO: that I have been using all these years): > Where will the package be available? -- Cecil - k5nwa
[toc] | [prev] | [next] | [standalone]
Page 13 of 14 — ← Prev page 1 … 11 12 [13] 14 Next page →
Back to top | Article view | comp.lang.forth
csiph-web