Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #42092 > unrolled thread
| Started by | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| First post | 2015-09-20 08:45 +0000 |
| Last post | 2015-11-09 13:21 -0800 |
| Articles | 11 on this page of 191 — 29 participants |
Back to article view | Back to comp.lang.forth
EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-09-20 08:45 +0000
Re: EuroForth 2015 paper deadline approaching Matthias Trute <matthias.trute@gmail.com> - 2015-09-20 06:34 -0700
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-09-21 20:11 +0200
Re: EuroForth 2015 paper deadline approaching Matthias Trute <matthias.trute@gmail.com> - 2015-09-23 11:29 -0700
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-09-23 21:03 +0200
Re: EuroForth 2015 paper deadline approaching Matthias Trute <matthias.trute@gmail.com> - 2015-09-27 03:02 -0700
Re: EuroForth 2015 paper deadline approaching Mark Wills <markwills1970@gmail.com> - 2015-09-21 01:13 -0700
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-09-21 09:26 +0000
Re: EuroForth 2015 paper deadline approaching JUERGEN <epldfpga@aol.com> - 2015-10-03 03:46 -0700
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-10-03 22:56 -0700
Re: EuroForth 2015 paper deadline approaching rickman <gnuarm@gmail.com> - 2015-10-04 02:44 -0400
Re: EuroForth 2015 paper deadline approaching JUERGEN <epldfpga@aol.com> - 2015-10-04 01:14 -0700
Re: EuroForth 2015 paper deadline approaching rickman <gnuarm@gmail.com> - 2015-10-04 05:08 -0400
Re: EuroForth 2015 paper deadline approaching JUERGEN <epldfpga@aol.com> - 2015-10-04 04:06 -0700
Re: EuroForth 2015 paper deadline approaching Richard Owlett <rowlett@cloud85.net> - 2015-10-04 07:25 -0500
Re: EuroForth 2015 paper deadline approaching JUERGEN <epldfpga@aol.com> - 2015-10-04 06:49 -0700
Re: EuroForth 2015 paper deadline approaching Mark Wills <markwills1970@gmail.com> - 2015-10-04 09:21 -0700
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-10-09 13:24 -0700
Re: EuroForth 2015 paper deadline approaching "WJ" <w_a_x_man@yahoo.com> - 2015-10-08 22:18 +0000
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-10-08 06:59 +0000
Re: EuroForth 2015 paper deadline approaching Mikael Nordman <oh2aun@gmail.com> - 2015-10-08 04:24 -0700
Re: EuroForth 2015 paper deadline approaching Mark Wills <markwills1970@gmail.com> - 2015-10-08 05:08 -0700
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-10-08 13:57 +0000
Re: EuroForth 2015 paper deadline approaching Mikael Nordman <oh2aun@gmail.com> - 2015-10-08 13:36 -0700
Re: EuroForth 2015 paper deadline approaching "Elizabeth D. Rather" <erather@forth.com> - 2015-10-08 13:50 -1000
Re: EuroForth 2015 paper deadline approaching Jason Damisch <jasondamisch@yahoo.com> - 2015-10-10 12:10 -0700
Re: EuroForth 2015 paper deadline approaching Paul Rubin <no.email@nospam.invalid> - 2015-10-08 18:10 -0700
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-10-10 14:10 +0000
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-10-10 23:12 -0700
Re: EuroForth 2015 paper deadline approaching visualforth@rocketmail.com - 2015-10-12 10:18 -0700
Re: EuroForth 2015 paper deadline approaching rickman <gnuarm@gmail.com> - 2015-10-12 14:02 -0400
Re: EuroForth 2015 paper deadline approaching "Elizabeth D. Rather" <erather@forth.com> - 2015-10-12 08:03 -1000
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-10-12 14:58 -0700
Re: EuroForth 2015 paper deadline approaching Coos Haak <chforth@hccnet.nl> - 2015-10-13 01:25 +0200
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-10-12 17:38 -0700
Re: EuroForth 2015 paper deadline approaching "Elizabeth D. Rather" <erather@forth.com> - 2015-10-12 16:39 -1000
Re: EuroForth 2015 paper deadline approaching rickman <gnuarm@gmail.com> - 2015-10-10 19:12 -0400
Re: EuroForth 2015 paper deadline approaching JUERGEN <epldfpga@aol.com> - 2015-10-08 07:31 -0700
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-10-17 22:44 +0200
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-10-17 21:47 -0700
Re: EuroForth 2015 paper deadline approaching rickman <gnuarm@gmail.com> - 2015-10-18 01:51 -0400
Re: EuroForth 2015 paper deadline approaching "Elizabeth D. Rather" <erather@forth.com> - 2015-10-17 20:26 -1000
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-10-18 21:34 +0200
Re: EuroForth 2015 paper deadline approaching stephen@mpeforth.com (Stephen Pelc) - 2015-10-19 17:00 +0000
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-10-20 01:51 +0200
Re: EuroForth 2015 paper deadline approaching "Elizabeth D. Rather" <erather@forth.com> - 2015-10-19 16:24 -1000
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-10-20 02:44 -0700
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-10-20 13:01 +0000
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-10-20 22:59 -0700
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-10-20 23:57 -0700
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-10-21 10:58 -0700
Re: EuroForth 2015 paper deadline approaching krishna.myneni@ccreweb.org - 2015-11-11 14:06 -0800
Re: EuroForth 2015 paper deadline approaching JUERGEN <epldfpga@aol.com> - 2015-11-11 14:48 -0800
Re: EuroForth 2015 paper deadline approaching Paul Rubin <no.email@nospam.invalid> - 2015-11-11 14:59 -0800
Re: EuroForth 2015 paper deadline approaching JUERGEN <epldfpga@aol.com> - 2015-11-12 05:28 -0800
Re: EuroForth 2015 paper deadline approaching Paul Rubin <no.email@nospam.invalid> - 2015-11-12 18:18 -0800
Re: EuroForth 2015 paper deadline approaching krishna.myneni@ccreweb.org - 2015-11-11 15:12 -0800
Re: EuroForth 2015 paper deadline approaching JUERGEN <epldfpga@aol.com> - 2015-11-12 05:35 -0800
Re: EuroForth 2015 paper deadline approaching krishna.myneni@ccreweb.org - 2015-11-12 06:24 -0800
Re: EuroForth 2015 paper deadline approaching Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-11-12 14:44 +0000
Re: EuroForth 2015 paper deadline approaching Paul Rubin <no.email@nospam.invalid> - 2015-11-11 15:18 -0800
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-10-20 12:36 +0000
Re: EuroForth 2015 paper deadline approaching JUERGEN <epldfpga@aol.com> - 2015-10-18 12:54 -0700
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-10-19 02:47 +0200
Re: EuroForth 2015 paper deadline approaching JUERGEN <epldfpga@aol.com> - 2015-10-08 07:24 -0700
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-10-08 15:10 +0000
Re: EuroForth 2015 paper deadline approaching JUERGEN <epldfpga@aol.com> - 2015-10-08 09:15 -0700
Re: EuroForth 2015 paper deadline approaching "WJ" <w_a_x_man@yahoo.com> - 2015-11-02 20:35 +0000
Re: EuroForth 2015 paper deadline approaching Ilya Tarasov <ilya74.tarasov@gmail.com> - 2015-10-13 17:30 -0700
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-10-13 19:36 -0700
Re: EuroForth 2015 paper deadline approaching lehs <skydda.barnen@gmail.com> - 2015-10-13 23:54 -0700
Re: EuroForth 2015 paper deadline approaching lehs <skydda.barnen@gmail.com> - 2015-10-14 00:04 -0700
Re: EuroForth 2015 paper deadline approaching lehs <skydda.barnen@gmail.com> - 2015-10-14 00:09 -0700
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-10-14 09:45 +0000
Re: EuroForth 2015 paper deadline approaching Hannu Vuolasaho <vuokkosetae@gmail.com> - 2015-10-14 14:54 +0300
Re: EuroForth 2015 paper deadline approaching Brad Eckert <hwfwguy@gmail.com> - 2015-10-28 10:13 -0700
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-10-28 11:38 -0700
Re: EuroForth 2015 paper deadline approaching Brad Eckert <hwfwguy@gmail.com> - 2015-10-30 22:03 -0700
Re: EuroForth 2015 paper deadline approaching JUERGEN <epldfpga@aol.com> - 2015-10-31 02:10 -0700
Re: EuroForth 2015 paper deadline approaching Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-10-31 02:50 -0700
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-10-31 18:58 +0100
Re: EuroForth 2015 paper deadline approaching JUERGEN <epldfpga@aol.com> - 2015-10-31 14:18 -0700
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-10-31 23:43 +0100
Re: EuroForth 2015 paper deadline approaching JUERGEN <epldfpga@aol.com> - 2015-11-07 10:44 -0800
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-07 23:02 +0100
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-10-31 14:48 -0700
Re: EuroForth 2015 paper deadline approaching Mark Wills <markwills1970@gmail.com> - 2015-11-02 01:03 -0800
Re: EuroForth 2015 paper deadline approaching Paul Rubin <no.email@nospam.invalid> - 2015-11-02 01:44 -0800
Re: EuroForth 2015 paper deadline approaching Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-11-02 01:59 -0800
Re: EuroForth 2015 paper deadline approaching Mark Wills <markwills1970@gmail.com> - 2015-11-02 02:19 -0800
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-11-02 17:32 -0800
Re: EuroForth 2015 paper deadline approaching Mark Wills <markwills1970@gmail.com> - 2015-11-02 02:14 -0800
Re: EuroForth 2015 paper deadline approaching "Elizabeth D. Rather" <erather@forth.com> - 2015-11-02 12:10 -1000
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-11-02 16:45 -0800
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-02 10:26 +0000
Re: EuroForth 2015 paper deadline approaching Paul Rubin <no.email@nospam.invalid> - 2015-11-02 02:57 -0800
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-02 16:06 +0000
Re: EuroForth 2015 paper deadline approaching Paul Rubin <no.email@nospam.invalid> - 2015-11-02 09:36 -0800
Re: EuroForth 2015 paper deadline approaching Lars Brinkhoff <lars.spam@nocrew.org> - 2015-11-02 21:18 +0100
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-03 11:56 +0000
Re: EuroForth 2015 paper deadline approaching Albert van der Horst <albert@spenarnc.xs4all.nl> - 2015-11-03 18:16 +0000
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-04 10:53 +0000
16-bit Forth for Linux Lars Brinkhoff <lars.spam@nocrew.org> - 2015-11-20 11:13 +0100
Re: 16-bit Forth for Linux Albert van der Horst <albert@spenarnc.xs4all.nl> - 2015-11-20 15:08 +0000
Re: 16-bit Forth for Linux Lars Brinkhoff <lars.spam@nocrew.org> - 2015-11-20 20:11 +0100
Re: EuroForth 2015 paper deadline approaching Mark Wills <markwills1970@gmail.com> - 2015-11-02 11:10 -0800
Re: EuroForth 2015 paper deadline approaching Paul Rubin <no.email@nospam.invalid> - 2015-11-02 12:43 -0800
Re: EuroForth 2015 paper deadline approaching Howerd <howerdo@yahoo.co.uk> - 2015-11-03 03:05 -0800
Re: EuroForth 2015 paper deadline approaching Paul Rubin <no.email@nospam.invalid> - 2015-11-03 11:11 -0800
Re: EuroForth 2015 paper deadline approaching Howerd <howerdo@yahoo.co.uk> - 2015-11-03 03:07 -0800
Re: EuroForth 2015 paper deadline approaching Paul Rubin <no.email@nospam.invalid> - 2015-11-03 11:15 -0800
Re: EuroForth 2015 paper deadline approaching "Elizabeth D. Rather" <erather@forth.com> - 2015-11-02 12:18 -1000
Re: EuroForth 2015 paper deadline approaching "Elizabeth D. Rather" <erather@forth.com> - 2015-11-02 12:07 -1000
Re: EuroForth 2015 paper deadline approaching Paul Rubin <no.email@nospam.invalid> - 2015-11-02 15:41 -0800
Re: EuroForth 2015 paper deadline approaching "Elizabeth D. Rather" <erather@forth.com> - 2015-11-02 20:27 -1000
Re: EuroForth 2015 paper deadline approaching stephen@mpeforth.com (Stephen Pelc) - 2015-11-03 11:00 +0000
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-03 11:28 +0000
Re: EuroForth 2015 paper deadline approaching stephen@mpeforth.com (Stephen Pelc) - 2015-11-03 12:18 +0000
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-03 17:03 +0000
Re: EuroForth 2015 paper deadline approaching stephen@mpeforth.com (Stephen Pelc) - 2015-11-03 19:29 +0000
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-04 14:47 +0000
Re: EuroForth 2015 paper deadline approaching "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-11-04 21:15 -0500
Re: EuroForth 2015 paper deadline approaching Coos Haak <chforth@hccnet.nl> - 2015-11-05 03:19 +0100
Re: EuroForth 2015 paper deadline approaching "Elizabeth D. Rather" <erather@forth.com> - 2015-11-04 16:37 -1000
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-11-04 20:54 -0800
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-05 06:32 +0000
Re: EuroForth 2015 paper deadline approaching "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-11-04 21:17 -0500
Re: EuroForth 2015 paper deadline approaching "Elizabeth D. Rather" <erather@forth.com> - 2015-11-04 16:44 -1000
Re: EuroForth 2015 paper deadline approaching Mark Wills <markwills1970@gmail.com> - 2015-11-05 01:24 -0800
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-05 14:50 +0000
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-11-05 12:49 -0800
CMFORTH Lars Brinkhoff <lars.spam@nocrew.org> - 2015-11-06 08:43 +0100
Re: EuroForth 2015 paper deadline approaching Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-11-02 10:46 +0000
Re: EuroForth 2015 paper deadline approaching Mark Wills <markwills1970@gmail.com> - 2015-11-02 05:52 -0800
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-02 14:52 +0000
Re: EuroForth 2015 paper deadline approaching Mark Wills <markwills1970@gmail.com> - 2015-11-02 08:06 -0800
Re: EuroForth 2015 paper deadline approaching Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-11-02 08:32 -0800
Re: EuroForth 2015 paper deadline approaching Albert van der Horst <albert@spenarnc.xs4all.nl> - 2015-11-02 20:04 +0000
Re: EuroForth 2015 paper deadline approaching Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-11-02 22:31 -0800
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-11-03 18:49 -0800
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-03 12:24 +0000
Re: EuroForth 2015 paper deadline approaching Albert van der Horst <albert@spenarnc.xs4all.nl> - 2015-11-03 19:45 +0000
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-03 22:30 +0100
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-04 10:42 +0000
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-04 14:08 +0100
Re: EuroForth 2015 paper deadline approaching Albert van der Horst <albert@spenarnc.xs4all.nl> - 2015-11-04 14:07 +0000
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-04 14:34 +0000
Re: EuroForth 2015 paper deadline approaching stephen@mpeforth.com (Stephen Pelc) - 2015-11-04 17:32 +0000
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-05 23:00 +0100
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-06 07:27 +0000
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-06 22:04 +0100
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-07 16:07 +0000
Re: EuroForth 2015 paper deadline approaching Albert van der Horst <albert@spenarnc.xs4all.nl> - 2015-11-04 13:58 +0000
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-04 15:04 +0100
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-04 14:30 +0000
Re: EuroForth 2015 paper deadline approaching Ilya Tarasov <ilya74.tarasov@gmail.com> - 2015-11-04 11:57 -0800
Re: EuroForth 2015 paper deadline approaching "Elizabeth D. Rather" <erather@forth.com> - 2015-11-04 12:06 -1000
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-11-04 14:53 -0800
Re: EuroForth 2015 paper deadline approaching Ilya Tarasov <ilya74.tarasov@gmail.com> - 2015-11-07 14:44 -0800
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-08 00:02 +0100
Re: EuroForth 2015 paper deadline approaching Ilya Tarasov <ilya74.tarasov@gmail.com> - 2015-11-08 15:22 -0800
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-09 01:15 +0100
Re: EuroForth 2015 paper deadline approaching Ilya Tarasov <ilya74.tarasov@gmail.com> - 2015-11-08 17:06 -0800
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-11-08 22:12 -0800
Re: EuroForth 2015 paper deadline approaching Ilya Tarasov <ilya74.tarasov@gmail.com> - 2015-11-10 16:17 -0800
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-11 02:57 +0100
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-11-10 19:56 -0800
Re: EuroForth 2015 paper deadline approaching Ilya Tarasov <ilya74.tarasov@gmail.com> - 2015-11-11 10:13 -0800
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-12 01:53 +0100
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-11-12 09:19 -0800
Re: EuroForth 2015 paper deadline approaching Ilya Tarasov <ilya74.tarasov@gmail.com> - 2015-11-13 17:30 -0800
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-11-14 20:31 -0800
Re: EuroForth 2015 paper deadline approaching Ilya Tarasov <ilya74.tarasov@gmail.com> - 2015-11-15 14:50 -0800
Re: EuroForth 2015 paper deadline approaching Alfred Singlestone <vitonis@gmail.com> - 2015-11-17 05:07 -0800
Re: EuroForth 2015 paper deadline approaching Ilya Tarasov <ilya74.tarasov@gmail.com> - 2015-11-18 22:20 -0800
Re: EuroForth 2015 paper deadline approaching stephen@mpeforth.com (Stephen Pelc) - 2015-11-02 09:27 +0000
Re: EuroForth 2015 paper deadline approaching anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-11-02 10:51 +0000
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-02 14:37 +0100
Re: EuroForth 2015 paper deadline approaching franck.bensusan@gmail.com - 2015-11-02 23:20 -0800
Re: EuroForth 2015 paper deadline approaching Albert van der Horst <albert@spenarnc.xs4all.nl> - 2015-11-03 10:01 +0000
Re: EuroForth 2015 paper deadline approaching Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-11-03 02:30 -0800
Re: EuroForth 2015 paper deadline approaching Albert van der Horst <albert@spenarnc.xs4all.nl> - 2015-11-03 18:08 +0000
Re: EuroForth 2015 paper deadline approaching franck.bensusan@gmail.com - 2015-11-03 06:05 -0800
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-03 19:35 +0100
Re: EuroForth 2015 paper deadline approaching franck.bensusan@gmail.com - 2015-11-03 12:27 -0800
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-03 22:37 +0100
Re: EuroForth 2015 paper deadline approaching franck.bensusan@gmail.com - 2015-11-03 14:39 -0800
Re: EuroForth 2015 paper deadline approaching Bernd Paysan <bernd.paysan@gmx.de> - 2015-11-04 14:54 +0100
Re: EuroForth 2015 paper deadline approaching Mark Wills <markwills1970@gmail.com> - 2015-11-04 06:21 -0800
Re: EuroForth 2015 paper deadline approaching hughaguilar96@gmail.com - 2015-10-31 15:00 -0700
Re: EuroForth 2015 paper deadline approaching Brad Eckert <hwfwguy@gmail.com> - 2015-11-09 13:21 -0800
Page 10 of 10 — ← Prev page 1 … 8 9 [10]
| From | Raimond Dragomir <raimond.dragomir@gmail.com> |
|---|---|
| Date | 2015-11-03 02:30 -0800 |
| Message-ID | <ecd44551-f5a0-4f44-9bcb-2b659ae6c78d@googlegroups.com> |
| In reply to | #43159 |
marți, 3 noiembrie 2015, 12:01:09 UTC+2, Albert van der Horst a scris: > franck.bensusan@gmail.com writes: > > >Le lundi 2 novembre 2015 14:37:59 UTC+1, Bernd Paysan a =E9crit=A0: > >>=20 > >> OOP packages should be able to coexist with each other, and probably shou= > >ld=20 > >> use common primitives to manipulate things like the current object. You= > >=20 > >> might want to swap the dot parsers in and out depending on which OOP pack= > >age=20 > >> you use in which part of your program. That's why the dot-parser of Mini= > >- > >> OOF2 is not called rec:dot-parser, but rec:moof2. > >>=20 > >> --=20 > >> Bernd Paysan > >> "If you want it done right, you have to do it yourself" > >> net2o ID: kQusJzA;7*?t=3Duy@X}1GWr!+0qqp_Cn176t4(dQ* > >> http://bernd-paysan.de/ > > >Hello, > > >Sorry if this is a known concept but what is this "current object" thing us= > >ed > >by all OOP extensions ?=20 > >Is it the object on top of the data stack ? If so, I'am a little > >puzzled by "manipulating the current object". > > >If not, well, I don't understand this concept... > > Well, I can tell you how it is in my micro OOP > You can access the fiethods (my classes don't make a distinction > between fields and methods) of the current object directly, without > the need to specify that object. (Like ``with'' in Pascal). > Then, of course, you need a means to change the current object. > That is done by using (calling) it. Like so. > > The class Point has no fields, only getters and setters (x y x! y! ) > > Point upper-left-corner > Point upper-right-corner > > upper-right-corner > 12 13 y! x! \ refers to urc > x . y . \ gives 12 13 > > upper-right-corner ( -- ) \ made current > x y ( -- n n ) \ of upper-right-corner > lower-left-corner ( -- ) \ made current > y! x! ( n n -- ) \ Squeezed empty, by copying coordinates from urc to llc. > > Hope this helps. > > >Franck > -- > 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 Nice! So the class objects put some kind of wordlist at the top of the search order, a wordlist that contains the class members? What if you want to completely remove such a wordlist? is it possible? Your class word creates objects that have this behaviour. What about having a generic class word that works like the objects? I mean, sometimes you have a pointer to such a class, not the object itself. And you want to access the members...
[toc] | [prev] | [next] | [standalone]
| From | Albert van der Horst <albert@spenarnc.xs4all.nl> |
|---|---|
| Date | 2015-11-03 18:08 +0000 |
| Message-ID | <5638f810$0$23862$e4fe514c@news.xs4all.nl> |
| In reply to | #43160 |
Raimond Dragomir <raimond.dragomir@gmail.com> writes: >mar=C8=9Bi, 3 noiembrie 2015, 12:01:09 UTC+2, Albert van der Horst a scris: >> franck.bensusan@gmail.com writes: >>=20 >> >Le lundi 2 novembre 2015 14:37:59 UTC+1, Bernd Paysan a =3DE9crit=3DA0: >> >>=3D20 >> >> OOP packages should be able to coexist with each other, and probably s= >hou=3D >> >ld=3D20 >> >> use common primitives to manipulate things like the current object. Y= >ou=3D >> >=3D20 >> >> might want to swap the dot parsers in and out depending on which OOP p= >ack=3D >> >age=3D20 >> >> you use in which part of your program. That's why the dot-parser of M= >ini=3D >> >- >> >> OOF2 is not called rec:dot-parser, but rec:moof2. >> >>=3D20 >> >> --=3D20 >> >> Bernd Paysan >> >> "If you want it done right, you have to do it yourself" >> >> net2o ID: kQusJzA;7*?t=3D3Duy@X}1GWr!+0qqp_Cn176t4(dQ* >> >> http://bernd-paysan.de/ >>=20 >> >Hello, >>=20 >> >Sorry if this is a known concept but what is this "current object" thing= > us=3D >> >ed >> >by all OOP extensions ?=3D20 >> >Is it the object on top of the data stack ? If so, I'am a little >> >puzzled by "manipulating the current object". >>=20 >> >If not, well, I don't understand this concept... >>=20 >> Well, I can tell you how it is in my micro OOP >> You can access the fiethods (my classes don't make a distinction >> between fields and methods) of the current object directly, without >> the need to specify that object. (Like ``with'' in Pascal). >> Then, of course, you need a means to change the current object. >> That is done by using (calling) it. Like so. >>=20 >> The class Point has no fields, only getters and setters (x y x! y! ) >>=20 >> Point upper-left-corner >> Point upper-right-corner >>=20 >> upper-right-corner >> 12 13 y! x! \ refers to urc >> x . y . \ gives 12 13 >>=20 >> upper-right-corner ( -- ) \ made current >> x y ( -- n n ) \ of upper-right-corner >> lower-left-corner ( -- ) \ made current >> y! x! ( n n -- ) \ Squeezed empty, by copying coordinates from urc to llc= >. >>=20 >> Hope this helps. >>=20 >> >Franck >> --=20 >> Albert van der Horst, UTRECHT,THE NETHERLANDS >> Economic growth -- being exponential -- ultimately falters. >> albert@spe&ar&c.xs4all.nl &=3Dn http://home.hccnet.nl/a.w.m.van.der.horst >Nice! >So the class objects put some kind of wordlist at the top of the search ord= >er, >a wordlist that contains the class members? >What if you want to completely remove such a wordlist? is it possible? >Your class word creates objects that have this behaviour. What about >having a generic class word that works like the objects? I mean, sometimes >you have a pointer to such a class, not the object itself. And you want >to access the members... I have one screen(!) devoted to creating the word class. 1] So don't expect something fancy. For each class there is one pointer, so each class has a current object. Like WITH in pascal really, WITH can be nested, if they refer to different structures. There are naming conventions. In the above example ^Point contains the pointer and you are allowed to store the like so data field of objects there. BUILD-Point lays down a Point object in memory and returns a pointer that can be stored into ^Point. Current object is inspired by stupid simple, not by the piling abstractions. I've yet to come accross a situation where sticking wordlist in would be beneficial. Like Elizabeth Rather, I find it hard to find situations where it pays off to make things more abstract or more complicated. My class is one notch up from CREATE DOES> and I use it all the time. Groetjes Albert 1] In all fairness, two underlying facilities are used: SWAP-DP (compile to an alternative area) FORMAT (manipulate strings and substitutions within strings.) Both one screen. -- 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 | franck.bensusan@gmail.com |
|---|---|
| Date | 2015-11-03 06:05 -0800 |
| Message-ID | <9485b0a0-f784-4b21-9442-54b722234f92@googlegroups.com> |
| In reply to | #43159 |
Le mardi 3 novembre 2015 11:01:09 UTC+1, Albert van der Horst a écrit : > Well, I can tell you how it is in my micro OOP > You can access the fiethods (my classes don't make a distinction > between fields and methods) of the current object directly, without > the need to specify that object. (Like ``with'' in Pascal). > Then, of course, you need a means to change the current object. > That is done by using (calling) it. Like so. > > The class Point has no fields, only getters and setters (x y x! y! ) > > Point upper-left-corner > Point upper-right-corner > > upper-right-corner > 12 13 y! x! \ refers to urc > x . y . \ gives 12 13 > > upper-right-corner ( -- ) \ made current > x y ( -- n n ) \ of upper-right-corner > lower-left-corner ( -- ) \ made current > y! x! ( n n -- ) \ Squeezed empty, by copying coordinates from urc to llc. > > Hope this helps. > > >Franck > -- > 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 Interesting, thank you. I think I understand this "current object" now. So "manipulating the current object" is just calling its name. No primitive needed here, no ? Does this mean that all objects created must have a name to be able to switch them to be "the current object" ? If yes, how do you create, for instance, a Rectangle class (with 2 points) and a method on rectangles that calculate its diagonal. Rectangle r1 Rectangle r2 .... \ init r1 & r2 with points r1 diag . r2 diag . Oforth is not working like that : - Objects don't have a name : they are created on the heap and the data stack hold object references. - When a method is called, it checks the top of the stack and call the correct implementation (polymorphism) according to this object. So, there is no "current object" here. Franck
[toc] | [prev] | [next] | [standalone]
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Date | 2015-11-03 19:35 +0100 |
| Message-ID | <n1aul0$p5d$1@dont-email.me> |
| In reply to | #43176 |
franck.bensusan@gmail.com wrote: > Interesting, thank you. I think I understand this "current object" now. > So "manipulating the current object" is just calling its name. > No primitive needed here, no ? Well, there's certainly some magic behind calling its name, and that manipulates the current object, e.g. saving the old current object on the return stack and setting the current object variable or register. > Does this mean that all objects created must have a name to > be able to switch them to be "the current object" ? Or an address, which then could go straight to the current object, e.g. by using a word like WITH or >O. > Oforth is not working like that : > - Objects don't have a name : they are created on the heap > and the data stack hold object references. > - When a method is called, it checks the top of the stack and > call the correct implementation (polymorphism) according to > this object. > > So, there is no "current object" here. Yes, on the axis of how OOPs differ, "has/doesn't have a current object" is one dimension. "Dimension", because it's not a simple yes/now answer. There are some hybrids like Anton's objects.fs, which has a current object, but uses it only for instance variables, not for method invocation. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o ID: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* http://bernd-paysan.de/
[toc] | [prev] | [next] | [standalone]
| From | franck.bensusan@gmail.com |
|---|---|
| Date | 2015-11-03 12:27 -0800 |
| Message-ID | <c731b517-3559-4152-a335-3c7f58e95ece@googlegroups.com> |
| In reply to | #43186 |
Le mardi 3 novembre 2015 19:35:19 UTC+1, Bernd Paysan a écrit : > franck.bensusan@gmail.com wrote: > > Interesting, thank you. I think I understand this "current object" now. > > So "manipulating the current object" is just calling its name. > > No primitive needed here, no ? > > Well, there's certainly some magic behind calling its name, and that > manipulates the current object, e.g. saving the old current object on the > return stack and setting the current object variable or register. > > > Does this mean that all objects created must have a name to > > be able to switch them to be "the current object" ? > > Or an address, which then could go straight to the current object, e.g. by > using a word like WITH or >O. I understand that, if objects are named, this object is "called" before invoking a method on it. Let's say, this pushes its address on the stack. But, do you say that, if an "unamed" object (well, its address) is already on the top of the stack, you can't call a method on it unless prefixing this call by WITH or >O ? If so, this is strange. Why not just let the method decide what to do without this prefix ? Like ... words... For instance, let's say + is a method (this is actually the case in Oforth, + is a polymorphic method). You would like to write : 1 2 + and not 1 2 WITH + no ? Well, perhap's there are some technical reasons into those OOP packages that require to set this "current object" for method invocation. But I find this constraint quite "heavy" for users. Mixing words and methods transparently (or being able to rewrite a word as a method or a method as a word without impact to the code) is also important. > > Oforth is not working like that : > > - Objects don't have a name : they are created on the heap > > and the data stack hold object references. > > - When a method is called, it checks the top of the stack and > > call the correct implementation (polymorphism) according to > > this object. > > > > So, there is no "current object" here. > > Yes, on the axis of how OOPs differ, "has/doesn't have a current object" is > one dimension. "Dimension", because it's not a simple yes/now answer. > There are some hybrids like Anton's objects.fs, which has a current object, > but uses it only for instance variables, not for method invocation. > In Oforth, instance variables are different from methods. For instance, if class Point has 2 instance variables x and y, you can directly access to instance variables values into implementations : Point method: sum @x @y + ; But this is not a "current object" neither. It is just that, when sum method is performed, the object on top of the stack is automatically removed from the stack and stored into the return stack, as a "self" parameter for this method. Franck
[toc] | [prev] | [next] | [standalone]
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Date | 2015-11-03 22:37 +0100 |
| Message-ID | <n1b9b8$88m$1@dont-email.me> |
| In reply to | #43194 |
franck.bensusan@gmail.com wrote: > In Oforth, instance variables are different from methods. > > For instance, if class Point has 2 instance variables x and y, > you can directly access to instance variables values into implementations > : > > Point method: sum > @x @y + ; > > But this is not a "current object" neither. It is just that, when sum > method is performed, the object on top of the stack is automatically > removed from the stack and stored into the return stack, as a "self" > parameter for this method. So you actually have a current object (stored on the return stack, which might be inconvenient if you want to use the return stack yourself, and still access instance variables), and like Anton use it for instance variables, but not for method invocation. The philosophy behind having a current object and words like WITH is to simply separate the two issues: using the current object and manipulating it. I've added a dot parser to Mini-OOF2 if you want the combination of calling and manipulating: .<method> takes the current object from the stack, calls the method, and then restores the current object. If you want to call several methods of the same object in a row, and maybe also access the instance variables (typical within the class implementation), you just don't use the . in front of the method name. When you do it the other way round, you always have to preceed those calls with "self" or "this" (or whatever you call your current object, maybe R@ or I as it is on the top of return stack?). -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o ID: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* http://bernd-paysan.de/
[toc] | [prev] | [next] | [standalone]
| From | franck.bensusan@gmail.com |
|---|---|
| Date | 2015-11-03 14:39 -0800 |
| Message-ID | <dcb4d04b-5898-480a-9248-2a31badec7b4@googlegroups.com> |
| In reply to | #43200 |
Le mardi 3 novembre 2015 22:37:51 UTC+1, Bernd Paysan a écrit : > franck.bensusan@gmail.com wrote: > > > In Oforth, instance variables are different from methods. > > > > For instance, if class Point has 2 instance variables x and y, > > you can directly access to instance variables values into implementations > > : > > > > Point method: sum > > @x @y + ; > > > > But this is not a "current object" neither. It is just that, when sum > > method is performed, the object on top of the stack is automatically > > removed from the stack and stored into the return stack, as a "self" > > parameter for this method. > > So you actually have a current object (stored on the return stack, which > might be inconvenient if you want to use the return stack yourself, and > still access instance variables), and like Anton use it for instance > variables, but not for method invocation. Yes, the current object is always stored on top of the return stack. Words like >R, R>, ... are banned from Oforth (you want to use the return stack, you declare a local) so the top of the stack and instance variables are always available. This current object is what is pushed on the stack when "self" is performed. self just pushes the top of the return stack on the data stack. But there is no "current object" stored into a global variable, a dedicated register of a auxiliary stack to save or restore. > The philosophy behind having a current object and words like WITH is to > simply separate the two issues: using the current object and manipulating > it. I've added a dot parser to Mini-OOF2 if you want the combination of > calling and manipulating: .<method> takes the current object from the stack, > calls the method, and then restores the current object. This is also the standard implementation of Oforth methods. As standard, there is no need for dot parser : you just use the method name, like words. - Remove the top of the data stack -> the receiver - Find the correct implementation for this method according to this object. - Allocate return stack for locals. - Push the receiver on top of the return stack - Begins the method code. > If you want to call several methods of the same object in a row, and maybe > also access the instance variables (typical within the class > implementation), you just don't use the . in front of the method name. When > you do it the other way round, you always have to preceed those calls with > "self" or "this" (or whatever you call your current object, maybe R@ or I as > it is on the top of return stack?). > It is "self", yes : the top of the return stack. But : 1) I almost never call several times methods on the same object. 2) I almost always call methods on objects returned by previous method calls. imo, it is much more profitable to have a clean syntax for the second case without having to save and restore the "current object" than trying to optimize the first one, the only potential gain being saving 1 self from time to time.
[toc] | [prev] | [next] | [standalone]
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Date | 2015-11-04 14:54 +0100 |
| Message-ID | <n1d2ii$rdk$1@dont-email.me> |
| In reply to | #43202 |
franck.bensusan@gmail.com wrote:
> Yes, the current object is always stored on top of the return stack.
> Words like >R, R>, ... are banned from Oforth (you want to use the return
> stack, you declare a local) so the top of the stack and instance variables
> are always available.
If your local stack differs from the return stack, easy. Anton did it the
other way round: the current object is a local. Gforth supports to declare
locals whenever you need them, so you can declare further locals and still
use the return stack.
> This current object is what is pushed on the stack when "self" is
> performed. self just pushes the top of the return stack on the data stack.
>
> But there is no "current object" stored into a global variable, a
> dedicated register of a auxiliary stack to save or restore.
Yes, it's only 50% of a real current object.
> This is also the standard implementation of Oforth methods. As standard,
> there is no need for dot parser : you just use the method name, like
> words. - Remove the top of the data stack -> the receiver
> - Find the correct implementation for this method according to this
> object. - Allocate return stack for locals.
> - Push the receiver on top of the return stack
> - Begins the method code.
You always have to do all of it, if you need it or not.
> It is "self", yes : the top of the return stack. But :
> 1) I almost never call several times methods on the same object.
> 2) I almost always call methods on objects returned by previous method
> calls.
>
> imo, it is much more profitable to have a clean syntax for the second case
> without having to save and restore the "current object" than trying to
> optimize the first one, the only potential gain being saving 1 self from
> time to time.
This is a good explanation why everybody makes his OOP different - different
programming styles need different notations.
Compare that to this method, written in a way that you see which context is
used: dpy is an object pointer; using the dot-parser to indicate method
called by object on stack.
: DOPRESS ( dx dy -- dx dy x y )
BEGIN BEGIN dpy .click? 0= WHILE dpy .moved?
IF 2dup dpy .mouse drop r@ execute
dpy .sync
THEN dpy .invoke dpy .do-idle
REPEAT dpy .click nip 1 and WHILE
2drop REPEAT dpy .moved! ;
Vs. using the current object way, using with/endwith:
: DOPRESS ( dx dy -- dx dy x y ) dpy with
BEGIN BEGIN click? 0= WHILE moved?
IF 2dup mouse drop endwith r@ execute
dpy with sync
THEN invoke do-idle
REPEAT click nip 1 and WHILE
2drop REPEAT moved! endwith ;
It's almost always calling methods of the dpy object, except the r@ EXECUTE
(the remainder of the code after DOPRESS; today I more likely would use a
quotation for that), which is in the object's own context.
The dot parser makes calling with current object on the stack almost as easy
as direct calling, so that's an optimization for your style. My style with
multiple calls of methods from the same object don't need it so much.
The main point here is that as long as you intent to use the OOP for
yourself only, you can optimize for your case, and pessimize for all other
cases, because you don't need them. We have probably 30 or more of these
OOP systems around. Nobody wants to use the OOP system of anybody else, and
the reason is obvious: It's all written tailored for one particular style.
To overcome this, the writer must accept that people have different needs
and different styles. One size does not fit all.
--
Bernd Paysan
"If you want it done right, you have to do it yourself"
net2o ID: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ*
http://bernd-paysan.de/
[toc] | [prev] | [next] | [standalone]
| From | Mark Wills <markwills1970@gmail.com> |
|---|---|
| Date | 2015-11-04 06:21 -0800 |
| Message-ID | <9fa2ef25-75ed-41ca-a69b-1d6e062cba56@googlegroups.com> |
| In reply to | #43224 |
On Wednesday, 4 November 2015 13:54:33 UTC, Bernd Paysan wrote: > We have probably 30 or more of these > OOP systems around. Nobody wants to use the OOP system of anybody else, and > the reason is obvious: It's all written tailored for one particular style. I think it's more a combination of NIH (not invented here) and Forth being so powerful, that it is actuall capable of using itself in which to implement a OOP system, whereas in other languages, it's simply impossible. That, and it's a notch on one's belt ;-)
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2015-10-31 15:00 -0700 |
| Message-ID | <2a3fcc45-8675-43ea-b54c-e77cd346ea2a@googlegroups.com> |
| In reply to | #43017 |
On Friday, October 30, 2015 at 10:03:04 PM UTC-7, Brad Eckert wrote: > Here's my suggestion. Come up with a fun, simple Forth that people like. Well, that is what I'm trying to do with FloatForth. Here is a quote from my document that I'm working on (not released yet): --------------------------------------------------------------------------- FloatForth is for use only on desktop-computers and is not for use on micro-controllers --- FloatForth can be used as a host for a cross-compiler for a micro-controller Forth --- standardization is not all that important with micro-controller Forths because the programs aren't going to be portable anyway due a lot of direct access of I/O and other resources. The data-stack in FloatForth is required to be 64 bits wide. There are two versions of FloatForth differing in their definition of what a number is: 1.) fixed-version A number is a signed 64-bit fixed-point with unity assumed to be 2^32. 2.) float-version A number is an IEEE-754 double-precision float (64 bit total size, with a 56-bit significand). It is possible that other versions may be introduced later with their own definition of what a number is --- BCD (binary-coded-decimal) would be a possibility --- so long as the number fits in 64 bits and it supports integers in the range +-2GB for use as addresses, then it should be fine. So, although the name is FloatForth, the language may not support floating-point. For the most part, FloatForth is intended to be implemented on 64-bit processors. FloatForth can be implemented on a 32-bit processor --- reasonable speed could be obtained if the float-version is used and there is a numeric coprocessor available. Addresses are limited to 32-bit (4GB) whether the processor is 64-bit or 32-bit. Addresses are signed (FloatForth doesn't support unsigned numbers) with the heap being in the negative and the dictionary being in the positive. --------------------------------------------------------------------------- I got this idea from Lua, which definitely qualifies as a fun and simple language. :-) Also, the "killer application" for FloatForth is CAM (Computer-Aided-Manufacturing) which involves generating gcode for CNC machines. My experience working as a machinist, is that machinists aren't going to use a big complicated programming language. ANS-Forth is quadruple as complicated as it needs to be, and Forth-200x is quadruple as complicated as ANS-Forth, so they won't be used. FloatForth just has "numbers" --- it doesn't distinguish between signed integers, unsigned integers and floating-point numbers --- I think that machinists will like this simplicity because it is the same as the pocket calculators that they have been using in which there is no distinction made between different kinds of numbers.
[toc] | [prev] | [next] | [standalone]
| From | Brad Eckert <hwfwguy@gmail.com> |
|---|---|
| Date | 2015-11-09 13:21 -0800 |
| Message-ID | <2930a133-79ea-46fe-9b41-1aa51f60288b@googlegroups.com> |
| In reply to | #43017 |
On Friday, October 30, 2015 at 10:03:04 PM UTC-7, Brad Eckert wrote: > Here's my suggestion. Come up with a fun, simple Forth that people like. People wanted to do colorForth but it was too out-there with no supportive infrastructure. That's not to say it can't be adapted to a wider audience. Maybe it should be targeted at the embedded crowd and a nice interactive GUI built. Decent support for integration with C environments would solve any performance issues. This is actually an important point. Chuck put many years of deep thought into the concepts of colorForth. It would be a shame to lose those concepts because they weren't packaged in a way suited to a wider audience. Although, those concepts are thankfully on the web so they won't really be lost. We have all benefited from Chuck's life work, and yet his most advanced concepts collect dust for the most part.
[toc] | [prev] | [standalone]
Page 10 of 10 — ← Prev page 1 … 8 9 [10]
Back to top | Article view | comp.lang.forth
csiph-web