Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #37787 > unrolled thread
| Started by | hughaguilar96@gmail.com |
|---|---|
| First post | 2015-03-31 15:13 -0700 |
| Last post | 2015-07-06 12:47 -0400 |
| Articles | 20 on this page of 509 — 42 participants |
Back to article view | Back to comp.lang.forth
bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-03-31 15:13 -0700
Re: bug in VFX --- IF does't work jfong@ms4.hinet.net - 2015-03-31 20:55 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-04-01 11:26 +0000
Re: bug in VFX --- IF does't work Jason Damisch <jasondamisch@yahoo.com> - 2015-04-01 08:39 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-04-01 17:35 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-12 15:18 -0700
Re: bug in VFX --- IF does't work Jan Coombs <Jan-54 <jenfhaomndgfwutc@murmic.plus.com>> - 2015-04-02 10:35 +0100
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-02 10:08 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-01 12:33 -0700
Re: bug in VFX --- IF does't work "Rod Pemberton" <bork@lllljunkqwer.cpm> - 2015-04-01 22:16 -0400
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-01 13:40 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-04-02 17:07 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-02 19:18 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-04-03 06:43 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-03 10:49 -0700
Re: bug in VFX --- IF does't work beeflo <beeflobill@gmail.com> - 2015-04-03 11:17 -0700
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-04-03 14:35 -0400
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-04-03 19:42 +0100
Re: bug in VFX --- IF does't work jkn_gg@nicorp.f9.co.uk - 2015-04-03 14:34 -0700
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-04-03 20:52 -0400
Re: bug in VFX --- IF does't work jkn_gg@nicorp.f9.co.uk - 2015-04-04 03:47 -0700
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-04 14:07 -0700
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-04-05 00:11 -0400
Re: bug in VFX --- IF does't work jkn_gg@nicorp.f9.co.uk - 2015-04-05 08:11 -0700
Re: bug in VFX --- IF does't work albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-03 23:50 +0000
Re: bug in VFX --- IF does't work Hans-Peter Diettrich <DrDiettrich1@aol.com> - 2015-04-04 05:44 +0200
Re: bug in VFX --- IF does't work Paul Rubin <no.email@nospam.invalid> - 2015-04-03 21:32 -0700
Re: bug in VFX --- IF does't work Hans-Peter Diettrich <DrDiettrich1@aol.com> - 2015-04-04 17:03 +0200
Re: bug in VFX --- IF does't work Paul Rubin <no.email@nospam.invalid> - 2015-04-04 21:56 -0700
Re: bug in VFX --- IF does't work Hans-Peter Diettrich <DrDiettrich1@aol.com> - 2015-04-05 18:11 +0200
Re: bug in VFX --- IF does't work Paul Rubin <no.email@nospam.invalid> - 2015-04-05 10:13 -0700
Re: bug in VFX --- IF does't work Hans-Peter Diettrich <DrDiettrich1@aol.com> - 2015-04-06 14:03 +0200
Re: bug in VFX --- IF does't work albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-06 14:44 +0000
Re: bug in VFX --- IF does't work Hans-Peter Diettrich <DrDiettrich1@aol.com> - 2015-04-07 11:02 +0200
Re: bug in VFX --- IF does't work Paul Rubin <no.email@nospam.invalid> - 2015-04-07 17:21 -0700
Re: bug in VFX --- IF does't work "WJ" <w_a_x_man@yahoo.com> - 2015-04-07 16:02 +0000
Re: bug in VFX --- IF does't work Paul Rubin <no.email@nospam.invalid> - 2015-04-07 11:06 -0700
Re: bug in VFX --- IF does't work Elizabeth D Rather <erather@forth.com> - 2015-04-03 18:52 -1000
Re: bug in VFX --- IF does't work "WJ" <w_a_x_man@yahoo.com> - 2015-04-05 03:54 +0000
Re: bug in VFX --- IF does't work Hans-Peter Diettrich <DrDiettrich1@aol.com> - 2015-04-05 18:21 +0200
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-05 21:47 -0700
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-12 14:41 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-12 23:20 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-12 18:40 -0700
Re: bug in VFX --- IF does't work "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-06-13 04:36 -0400
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-13 23:12 -0700
Re: bug in VFX --- IF does't work "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-06-14 09:53 -0400
Re: bug in VFX --- IF does't work Michael Barry <barrym95838@yahoo.com> - 2015-06-14 18:38 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-15 21:03 +0100
Re: bug in VFX --- IF does't work Michael Barry <barrym95838@yahoo.com> - 2015-06-15 19:38 -0700
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-06-15 22:54 -0400
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-16 10:01 +0100
Re: bug in VFX --- IF does't work Michael Barry <barrym95838@yahoo.com> - 2015-06-16 18:25 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-17 10:11 +0100
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-06-15 22:49 -0400
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-15 21:56 -0700
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-06-16 00:11 -0700
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-16 07:21 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-16 19:45 -0700
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-17 10:34 +0000
Re: bug in VFX --- IF does't work Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-17 08:49 -0700
Re: bug in VFX --- IF does't work mhx@iae.nl - 2015-06-17 13:50 -0700
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-17 18:36 -0700
Re: bug in VFX --- IF does't work Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-17 23:44 -0700
Re: bug in VFX --- IF does't work "Elizabeth D. Rather" <erather@forth.com> - 2015-06-17 21:14 -1000
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-06-18 00:15 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-18 09:27 +0100
Re: bug in VFX --- IF does't work Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-18 02:04 -0700
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-06-18 03:32 -0700
Re: bug in VFX --- IF does't work Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-18 04:19 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-18 12:31 +0000
Re: bug in VFX --- IF does't work Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-18 05:57 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-18 12:21 +0000
Re: bug in VFX --- IF does't work "Elizabeth D. Rather" <erather@forth.com> - 2015-06-18 08:01 -1000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-18 12:11 -0700
Re: bug in VFX --- IF does't work Walter Banks <walter@bytecraft.com> - 2015-06-18 17:25 -0400
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-18 22:56 +0200
Re: bug in VFX --- IF does't work coos <chforth@hccnet.nl> - 2015-06-18 18:54 +0200
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-18 10:53 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-18 21:31 +0100
Re: bug in VFX --- IF does't work Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-18 23:58 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-19 08:23 +0100
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-06-19 01:01 -0700
Re: bug in VFX --- IF does't work Thomas Östreicher <thomas.oestreicher@gmail.com> - 2015-06-19 01:07 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-19 09:38 +0000
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-06-19 02:51 -0700
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-20 16:35 +0000
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-06-20 21:28 -0700
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-20 21:33 -0700
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-06-20 21:49 -0700
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-21 14:01 +0000
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-21 14:19 +0000
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-22 13:16 +0000
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-22 16:53 +0000
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-23 15:39 +0000
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-23 18:11 +0000
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-23 22:16 +0200
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-23 23:26 +0000
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-24 03:23 +0200
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-24 08:04 +0000
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-24 14:46 +0200
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-24 13:03 +0000
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-24 15:05 +0100
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-24 14:32 +0000
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-24 14:20 +0000
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-24 20:04 +0200
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-24 16:08 +0200
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-26 08:07 +0100
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-26 08:55 +0000
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-27 00:56 +0200
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-26 18:06 +0100
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-27 01:00 +0200
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-27 11:07 +0100
Re: bug in VFX --- IF does't work Matthias Trute <matthias.trute@gmail.com> - 2015-06-27 12:04 -0700
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-27 21:14 +0200
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-20 16:26 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-20 21:55 -0700
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-21 14:26 +0000
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-22 00:29 +0100
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-22 03:24 +0200
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-22 07:49 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-21 21:16 -0700
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-06-22 02:09 -0700
Re: bug in VFX --- IF does't work "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-06-22 05:57 -0400
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-21 14:27 +0000
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-22 11:58 +0000
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-06-19 01:04 -0700
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-20 16:17 +0000
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-06-19 00:55 -0700
Re: bug in VFX --- IF does't work Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-19 02:42 -0700
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-06-19 03:56 -0400
Re: bug in VFX --- IF does't work Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-19 02:47 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-19 11:37 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-19 19:56 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-21 21:23 +0100
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-22 08:39 +0000
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-22 11:27 +0100
Re: bug in VFX --- IF does't work "WJ" <w_a_x_man@yahoo.com> - 2015-06-22 16:07 +0000
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-21 14:56 +0000
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-06-19 00:40 -0700
Re: bug in VFX --- IF does't work Ron Aaron <rambamist@gmail.com> - 2015-06-19 10:55 +0300
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-21 14:43 +0000
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-06-22 02:05 -0700
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-22 16:41 +0000
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-19 12:55 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-18 10:00 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-18 20:56 +0100
Re: bug in VFX --- IF does't work Hannu Vuolasaho <vuokkosetae@gmail.com> - 2015-06-19 03:13 +0300
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-19 08:37 +0100
WAS: bug in VFX... IS: More rants from Rantman of Rantland rickman <gnuarm@gmail.com> - 2015-06-18 16:33 -0400
Re: WAS: bug in VFX... IS: More rants from Rantman of Rantland "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-06-19 05:19 -0400
Re: WAS: bug in VFX... IS: More rants from Rantman of Rantland Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-06-19 13:38 +0100
Re: WAS: bug in VFX... IS: More rants from Rantman of Rantland rickman <gnuarm@gmail.com> - 2015-06-19 12:29 -0400
Re: WAS: bug in VFX... IS: More rants from Rantman of Rantland "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-06-19 17:53 -0400
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-19 12:07 +0000
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-19 12:55 +0000
The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-20 15:36 +0000
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-06-20 14:01 -0400
Re: The meaning of xt in Forth-94 "Elizabeth D. Rather" <erather@forth.com> - 2015-06-20 08:33 -1000
Re: The meaning of xt in Forth-94 hughaguilar96@gmail.com - 2015-06-20 21:18 -0700
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-21 13:09 +0000
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) stephen@mpeforth.com (Stephen Pelc) - 2015-06-21 14:50 +0000
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-21 23:58 +0200
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) stephen@mpeforth.com (Stephen Pelc) - 2015-06-22 10:54 +0000
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-22 15:52 +0000
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) stephen@mpeforth.com (Stephen Pelc) - 2015-06-22 17:08 +0000
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-23 16:43 +0000
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-22 20:19 +0200
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-22 08:47 +0000
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) stephen@mpeforth.com (Stephen Pelc) - 2015-06-22 13:58 +0000
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-22 15:37 +0000
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) stephen@mpeforth.com (Stephen Pelc) - 2015-06-22 17:02 +0000
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-23 16:29 +0000
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) stephen@mpeforth.com (Stephen Pelc) - 2015-06-23 18:18 +0000
Re: The meaning of xt in Forth-94 (was: bug in VFX --- IF does't work) Mark Wills <markwills1970@gmail.com> - 2015-06-23 00:42 -0700
Re: The meaning of xt in Forth-94 "Elizabeth D. Rather" <erather@forth.com> - 2015-06-22 21:47 -1000
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-23 02:42 -0700
Re: The meaning of xt in Forth-94 Mark Wills <markwills1970@gmail.com> - 2015-06-23 03:38 -0700
Re: The meaning of xt in Forth-94 stephen@mpeforth.com (Stephen Pelc) - 2015-06-23 12:55 +0000
Re: The meaning of xt in Forth-94 Mark Wills <markwills1970@gmail.com> - 2015-06-23 06:55 -0700
Re: The meaning of xt in Forth-94 peter.m.falth@gmail.com - 2015-06-23 08:29 -0700
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-23 16:47 +0000
Re: The meaning of xt in Forth-94 stephen@mpeforth.com (Stephen Pelc) - 2015-06-23 22:48 +0000
Re: The meaning of xt in Forth-94 hughaguilar96@gmail.com - 2015-06-24 18:13 -0700
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-06-25 13:40 +0100
Re: The meaning of xt in Forth-94 Mark Wills <markwills1970@gmail.com> - 2015-06-25 06:29 -0700
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-25 08:13 -0700
Re: The meaning of xt in Forth-94 stephen@mpeforth.com (Stephen Pelc) - 2015-06-25 16:33 +0000
Re: The meaning of xt in Forth-94 hughaguilar96@gmail.com - 2015-06-25 13:45 -0700
Re: The meaning of xt in Forth-94 stephen@mpeforth.com (Stephen Pelc) - 2015-06-26 05:54 +0000
Re: The meaning of xt in Forth-94 hughaguilar96@gmail.com - 2015-06-27 21:08 -0700
Re: The meaning of xt in Forth-94 Mark Wills <markwills1970@gmail.com> - 2015-06-26 03:44 -0700
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-26 03:52 -0700
Re: The meaning of xt in Forth-94 franck.bensusan@gmail.com - 2015-06-26 08:54 -0700
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-27 01:09 +0200
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-06-27 11:00 +0100
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-27 15:23 +0200
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-27 16:31 +0000
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-27 21:11 +0200
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-28 13:41 +0000
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-29 03:09 +0200
Re: The meaning of xt in Forth-94 mhx@iae.nl - 2015-06-27 06:42 -0700
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-06-28 13:21 +0100
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-06-26 12:20 +0100
Re: The meaning of xt in Forth-94 hughaguilar96@gmail.com - 2015-07-12 19:43 -0700
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-28 14:09 +0000
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-28 10:21 -0700
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-28 14:26 +0000
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-29 03:21 +0200
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-30 07:14 +0000
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-07-01 00:33 +0200
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-07-04 13:58 +0000
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-07-05 00:18 +0200
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-05 07:33 +0100
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-05 08:28 +0100
Re: The meaning of xt in Forth-94 stephen@mpeforth.com (Stephen Pelc) - 2015-07-05 12:22 +0000
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-07-06 16:03 +0000
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-06 18:40 +0100
Re: The meaning of xt in Forth-94 stephen@mpeforth.com (Stephen Pelc) - 2015-07-06 20:36 +0000
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-07 07:18 +0100
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-07-07 07:17 +0000
Re: The meaning of xt in Forth-94 Paul Rubin <no.email@nospam.invalid> - 2015-06-28 19:32 -0700
Re: The meaning of xt in Forth-94 "Elizabeth D. Rather" <erather@forth.com> - 2015-06-28 19:32 -1000
Re: The meaning of xt in Forth-94 Paul Rubin <no.email@nospam.invalid> - 2015-06-29 15:06 -0700
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-30 07:48 +0000
Re: The meaning of xt in Forth-94 franck.bensusan@gmail.com - 2015-06-30 03:38 -0700
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-30 04:44 -0700
Re: The meaning of xt in Forth-94 franck.bensusan@gmail.com - 2015-07-01 02:49 -0700
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-07-01 04:43 -0700
Re: The meaning of xt in Forth-94 rickman <gnuarm@gmail.com> - 2015-07-02 02:16 -0400
Re: The meaning of xt in Forth-94 Paul Rubin <no.email@nospam.invalid> - 2015-07-01 23:24 -0700
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-07-02 00:10 -0700
Re: The meaning of xt in Forth-94 Paul Rubin <no.email@nospam.invalid> - 2015-07-02 01:51 -0700
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-07-02 12:49 +0000
Re: The meaning of xt in Forth-94 "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-07-02 18:02 -0400
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-07-04 14:31 +0000
Re: The meaning of xt in Forth-94 Mark Wills <markwills1970@gmail.com> - 2015-06-30 01:55 -0700
Re: The meaning of xt in Forth-94 hughaguilar96@gmail.com - 2015-07-01 20:32 -0700
Re: The meaning of xt in Forth-94 Mark Wills <markwills1970@gmail.com> - 2015-07-02 02:40 -0700
Re: The meaning of xt in Forth-94 hughaguilar96@gmail.com - 2015-07-02 22:40 -0700
Re: The meaning of xt in Forth-94 "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-07-03 04:32 -0400
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-07-03 03:03 -0700
Re: The meaning of xt in Forth-94 Mark Wills <markwills1970@gmail.com> - 2015-07-03 03:16 -0700
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-03 22:06 +0100
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-07-03 22:39 -0700
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-07-04 14:45 +0000
Re: The meaning of xt in Forth-94 hughaguilar96@gmail.com - 2015-07-04 11:39 -0700
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-04 19:55 +0100
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-07-04 20:54 -0700
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-05 07:18 +0100
Re: The meaning of xt in Forth-94 "Elizabeth D. Rather" <erather@forth.com> - 2015-07-04 21:47 -1000
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-07-05 01:49 -0700
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-05 10:30 +0100
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-07-05 03:09 -0700
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-05 16:29 +0100
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-07-05 09:49 -0700
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-05 22:10 +0100
Re: The meaning of xt in Forth-94 Paul Rubin <no.email@nospam.invalid> - 2015-07-05 14:54 -0700
Re: The meaning of xt in Forth-94 "Elizabeth D. Rather" <erather@forth.com> - 2015-07-05 12:41 -1000
Re: The meaning of xt in Forth-94 Paul Rubin <no.email@nospam.invalid> - 2015-07-05 15:47 -0700
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-07-06 00:57 +0200
Re: The meaning of xt in Forth-94 Paul Rubin <no.email@nospam.invalid> - 2015-07-05 16:08 -0700
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-07-06 01:36 +0200
Re: The meaning of xt in Forth-94 Paul Rubin <no.email@nospam.invalid> - 2015-07-05 17:25 -0700
Re: The meaning of xt in Forth-94 "Elizabeth D. Rather" <erather@forth.com> - 2015-07-05 13:15 -1000
Re: The meaning of xt in Forth-94 Mark Wills <markwills1970@gmail.com> - 2015-07-06 02:05 -0700
Re: The meaning of xt in Forth-94 hughaguilar96@gmail.com - 2015-07-05 19:46 -0700
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-07-06 07:57 +0000
Re: The meaning of xt in Forth-94 Paul Rubin <no.email@nospam.invalid> - 2015-07-06 18:53 -0700
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-07-07 07:37 +0000
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-07-08 05:18 +0000
Re: The meaning of xt in Forth-94 Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-07-08 07:59 +0100
Re: The meaning of xt in Forth-94 Paul Rubin <no.email@nospam.invalid> - 2015-07-08 12:06 -0700
Re: The meaning of xt in Forth-94 hughaguilar96@gmail.com - 2015-07-08 20:08 -0700
Re: The meaning of xt in Forth-94 Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-07-09 08:31 +0100
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-09 14:06 +0100
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-09 14:09 +0100
Re: The meaning of xt in Forth-94 Paul Rubin <no.email@nospam.invalid> - 2015-07-09 13:34 -0700
Re: The meaning of xt in Forth-94 Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-07-10 20:27 +0100
Re: The meaning of xt in Forth-94 Paul Rubin <no.email@nospam.invalid> - 2015-07-10 12:46 -0700
Re: The meaning of xt in Forth-94 Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-07-10 21:48 +0100
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-07-08 17:02 +0200
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-08 17:48 +0100
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-07-08 20:58 +0200
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-08 20:19 +0100
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-07-08 21:48 +0200
Re: The meaning of xt in Forth-94 "Alex McDonald" <blog@rivadpm.com> - 2015-07-09 00:47 +0100
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-07-09 04:56 +0000
Re: The meaning of xt in Forth-94 hughaguilar96@gmail.com - 2015-07-11 14:34 -0700
Re: The meaning of xt in Forth-94 Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-07-07 08:09 +0100
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-07-07 16:32 +0200
Re: The meaning of xt in Forth-94 coos <chforth@hccnet.nl> - 2015-07-07 16:43 +0200
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-07-07 15:16 +0000
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-07-07 22:14 +0200
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-07-08 02:06 +0000
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-07-07 14:57 +0000
Re: The meaning of xt in Forth-94 Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-07-07 22:51 +0100
Re: The meaning of xt in Forth-94 "Elizabeth D. Rather" <erather@forth.com> - 2015-07-07 13:11 -1000
Re: The meaning of xt in Forth-94 hughaguilar96@gmail.com - 2015-07-07 19:34 -0700
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-07-06 20:47 -0700
Re: The meaning of xt in Forth-94 hughaguilar96@gmail.com - 2015-07-06 21:55 -0700
Re: The meaning of xt in Forth-94 "Elizabeth D. Rather" <erather@forth.com> - 2015-07-05 08:53 -1000
Re: The meaning of xt in Forth-94 Mark Wills <markwills1970@gmail.com> - 2015-07-06 01:56 -0700
Re: The meaning of xt in Forth-94 "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-06-23 18:13 -0400
Re: The meaning of xt in Forth-94 Mark Wills <markwills1970@gmail.com> - 2015-06-24 01:44 -0700
Re: The meaning of xt in Forth-94 "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-06-24 20:07 -0400
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-25 17:05 +0000
Re: The meaning of xt in Forth-94 Mark Wills <markwills1970@gmail.com> - 2015-06-24 02:08 -0700
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-24 04:53 -0700
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-24 04:57 -0700
Re: The meaning of xt in Forth-94 Mark Wills <markwills1970@gmail.com> - 2015-06-24 05:46 -0700
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-24 07:05 -0700
Re: The meaning of xt in Forth-94 stephen@mpeforth.com (Stephen Pelc) - 2015-06-24 14:40 +0000
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-24 10:12 -0700
Re: The meaning of xt in Forth-94 stephen@mpeforth.com (Stephen Pelc) - 2015-06-24 20:35 +0000
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-24 15:01 +0000
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-24 08:58 -0700
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-24 09:54 -0700
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-28 16:40 +0000
Re: The meaning of xt in Forth-94 "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-06-28 15:10 -0400
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-28 23:32 -0700
Re: The meaning of xt in Forth-94 "Elizabeth D. Rather" <erather@forth.com> - 2015-06-28 21:37 -1000
Re: The meaning of xt in Forth-94 Raimond Dragomir <raimond.dragomir@gmail.com> - 2015-06-29 01:38 -0700
Re: The meaning of xt in Forth-94 Mark Wills <markwills1970@gmail.com> - 2015-06-24 08:53 -0700
Re: The meaning of xt in Forth-94 "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-06-24 20:08 -0400
Re: The meaning of xt in Forth-94 anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-23 10:30 +0000
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-23 22:58 +0200
Re: The meaning of xt in Forth-94 Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-23 23:49 +0200
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-06-19 15:07 +0200
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-06-20 16:09 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-22 16:24 -0700
Re: bug in VFX --- IF does't work "WJ" <w_a_x_man@yahoo.com> - 2015-06-15 17:41 +0000
Re: bug in VFX --- IF does't work "WJ" <w_a_x_man@yahoo.com> - 2015-06-15 16:54 +0000
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-06-15 22:57 -0400
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-13 10:51 +0000
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-06-13 12:57 +0100
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-13 21:53 -0700
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-13 22:41 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-14 11:42 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-14 09:26 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-14 23:15 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-14 16:39 -0700
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-14 15:21 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-06-14 23:20 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-14 16:48 -0700
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-14 17:52 -0700
Re: bug in VFX --- IF does't work Doug Hoffman <glidedog@gmail.com> - 2015-06-14 21:13 -0400
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-06-14 20:09 -0700
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-03 10:25 -0700
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-04-03 14:43 -0400
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-04-03 20:14 +0100
Re: bug in VFX --- IF does't work jfong@ms4.hinet.net - 2015-04-03 23:16 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-04-03 20:02 +0100
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-03 20:46 +0000
Re: bug in VFX --- IF does't work krishna.myneni@ccreweb.org - 2015-04-04 06:43 -0700
Re: bug in VFX --- IF does't work albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-04 17:31 +0000
Re: bug in VFX --- IF does't work krishna.myneni@ccreweb.org - 2015-04-04 15:54 -0700
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-04 21:01 -0700
Re: bug in VFX --- IF does't work "WJ" <w_a_x_man@yahoo.com> - 2015-04-06 04:48 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-04 13:57 -0700
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-04-05 00:16 -0400
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-05 10:11 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-05 14:37 -0700
Re: bug in VFX --- IF does't work "WJ" <w_a_x_man@yahoo.com> - 2015-04-06 04:52 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-05 21:58 -0700
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-06 13:56 +0000
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-04-06 22:22 +0200
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-06 18:09 -0700
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-07 14:30 +0000
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-04-07 15:43 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-10 19:55 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-04-11 15:51 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-11 16:25 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-04-12 10:22 +0000
Re: bug in VFX --- IF does't work albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-12 10:48 +0000
Re: bug in VFX --- IF does't work albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-12 10:53 +0000
Re: bug in VFX --- IF does't work Coos Haak <chforth@hccnet.nl> - 2015-04-12 14:18 +0200
Re: bug in VFX --- IF does't work Coos Haak <chforth@hccnet.nl> - 2015-04-12 14:35 +0200
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-13 12:36 +0000
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-04-13 06:00 -0700
Re: bug in VFX --- IF does't work Coos Haak <chforth@hccnet.nl> - 2015-04-13 21:02 +0200
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-04-13 13:32 -0700
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-12 09:40 -0700
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-04-12 13:38 -0400
Re: bug in VFX --- IF does't work albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-12 18:55 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-13 00:07 -0700
Re: bug in VFX --- IF does't work albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-13 08:07 +0000
Re: bug in VFX --- IF does't work "WJ" <w_a_x_man@yahoo.com> - 2015-05-12 23:09 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-05-12 20:35 -0700
Re: bug in VFX --- IF does't work albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-05-13 10:10 +0000
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-05-13 15:58 -0400
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-05-13 13:13 -0700
Re: bug in VFX --- IF does't work albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-05-14 11:40 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-05-14 18:48 -0700
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-06-12 21:51 -0400
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-04-13 00:13 +0100
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-12 20:43 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-04-13 09:53 +0100
Re: bug in VFX --- IF does't work albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-14 09:46 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-14 10:01 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-04-14 18:24 +0100
Re: bug in VFX --- IF does't work "Rod Pemberton" <bork@lllljunkqwer.cpm> - 2015-04-14 17:17 -0400
Re: bug in VFX --- IF does't work Ron Aaron <rambamist@gmail.com> - 2015-04-13 18:08 +0300
Re: bug in VFX --- IF does't work "Rod Pemberton" <bork@lllljunkqwer.cpm> - 2015-04-06 22:07 -0400
Re: bug in VFX --- IF does't work "Elizabeth D. Rather" <erather@forth.com> - 2015-04-06 16:44 -1000
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-04-07 11:09 +0000
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-07 14:49 +0000
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-04-08 01:58 +0100
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-20 23:21 -0700
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-04-21 02:10 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-04-21 10:41 +0000
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-04-21 13:31 +0100
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-04-21 06:00 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-04-21 14:09 +0100
Re: bug in VFX --- IF does't work Lars Brinkhoff <lars.spam@nocrew.org> - 2015-04-22 10:59 +0200
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-04-22 11:41 +0000
Re: bug in VFX --- IF does't work Lars Brinkhoff <lars.spam@nocrew.org> - 2015-04-22 14:13 +0200
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-22 14:06 +0000
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-04-22 15:42 +0000
Re: bug in VFX --- IF does't work albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-22 15:57 +0000
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-22 16:43 +0000
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-04-24 05:35 +0200
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-24 11:22 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-24 11:18 -0700
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-04-25 01:21 +0200
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-25 16:49 +0000
Re: bug in VFX --- IF does't work Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-05-03 21:07 +0100
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-05-03 23:25 +0100
Re: bug in VFX --- IF does't work gwj.nexus@gmail.com - 2015-05-05 10:53 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-05-05 19:10 +0100
Re: bug in VFX --- IF does't work Gerry <gerry@jackson9000.fsnet.co.uk> - 2015-05-06 21:41 +0100
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-05-07 11:05 +0100
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-08 11:35 +0000
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-06 14:09 +0000
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-05-04 03:08 +0200
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-05-04 09:23 +0100
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-05-04 20:32 +0200
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-06 13:26 +0000
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-05-06 20:00 +0200
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-05-06 13:24 -0700
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-08 12:07 +0000
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-05-08 18:26 +0100
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-05-09 01:10 +0200
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-12 16:13 +0000
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-05-13 00:11 +0200
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-04 16:58 +0000
Re: bug in VFX --- IF does't work gwj.nexus@gmail.com - 2015-05-05 11:24 -0700
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-06 13:13 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-24 13:11 -0700
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-25 21:05 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-04-21 14:06 +0100
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-22 20:05 -0700
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-23 05:57 +0000
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-04-23 10:50 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-24 11:59 -0700
Re: bug in VFX --- IF does't work "WJ" <w_a_x_man@yahoo.com> - 2015-05-12 23:18 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-05-12 20:24 -0700
Re: bug in VFX --- IF does't work "Elizabeth D. Rather" <erather@forth.com> - 2015-04-24 08:56 -1000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-24 12:09 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-04-24 22:29 +0100
Re: bug in VFX --- IF does't work "WJ" <w_a_x_man@yahoo.com> - 2015-06-15 17:54 +0000
Re: bug in VFX --- IF does't work Jason Damisch <jasondamisch@yahoo.com> - 2015-04-02 09:04 -0700
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-02 21:04 -0700
Re: bug in VFX --- IF does't work albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-03 10:48 +0000
Re: bug in VFX --- IF does't work Hans Bezemer <the.beez.speaks@gmail.com> - 2015-04-10 17:52 +0200
Re: bug in VFX --- IF does't work albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-10 16:13 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-11 16:56 -0700
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-12 09:28 -0700
Re: bug in VFX --- IF does't work Jason Damisch <jasondamisch@yahoo.com> - 2015-04-03 10:26 -0700
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-04-05 21:54 -0700
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-04-26 01:20 +0200
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-26 15:09 +0000
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-04-27 03:13 +0200
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-01 14:59 +0000
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-05-01 19:38 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-05-01 16:59 -0700
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-02 15:56 +0000
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-05-01 22:45 +0200
Re: bug in VFX --- IF does't work JennyB <jennybrien@googlemail.com> - 2015-05-02 02:58 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-05-02 11:51 +0000
Re: bug in VFX --- IF does't work albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-05-02 12:25 +0000
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-02 16:45 +0000
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-05-02 19:12 +0100
Re: bug in VFX --- IF does't work anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-05-03 16:23 +0000
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-05-03 15:47 -0700
Re: bug in VFX --- IF does't work Jan Coombs <Jan-54 <jenfhaomndgfwutc@murmic.plus.com>> - 2015-05-04 10:11 +0100
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-05-04 09:16 -0700
Re: bug in VFX --- IF does't work roman.pavlyuk.0@gmail.com - 2015-05-04 10:15 -0700
Re: bug in VFX --- IF does't work "WJ" <w_a_x_man@yahoo.com> - 2015-06-15 23:35 +0000
Re: bug in VFX --- IF does't work Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-02 02:31 -0700
Re: bug in VFX --- IF does't work stephen@mpeforth.com (Stephen Pelc) - 2015-07-02 17:20 +0000
Re: bug in VFX --- IF does't work Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-02 15:40 -0700
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-07-02 19:55 -0400
Re: bug in VFX --- IF does't work Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-02 19:43 -0700
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-07-02 23:08 -0400
Re: bug in VFX --- IF does't work Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-02 21:56 -0700
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-07-03 01:25 -0400
Re: bug in VFX --- IF does't work hughaguilar96@gmail.com - 2015-07-02 23:00 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-07-03 22:25 +0100
Re: bug in VFX --- IF does't work Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-03 00:50 -0700
Re: bug in VFX --- IF does't work Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-03 18:21 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-07-04 13:09 +0100
Re: bug in VFX --- IF does't work Ching-Tang Tseng <ilikeforth@gmail.com> - 2015-07-04 15:01 -0700
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-07-05 08:49 +0100
Re: bug in VFX --- IF does't work Bernd Paysan <bernd.paysan@gmx.de> - 2015-07-05 15:23 +0200
Re: bug in VFX --- IF does't work "Alex McDonald" <blog@rivadpm.com> - 2015-07-05 15:56 +0100
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-07-05 12:21 -0400
Re: bug in VFX --- IF does't work Mark Wills <markwills1970@gmail.com> - 2015-07-06 01:45 -0700
Re: bug in VFX --- IF does't work rickman <gnuarm@gmail.com> - 2015-07-06 12:47 -0400
Page 17 of 26 — ← Prev page 1 … 15 16 [17] 18 19 … 26 Next page →
| From | Raimond Dragomir <raimond.dragomir@gmail.com> |
|---|---|
| Date | 2015-06-28 23:32 -0700 |
| Subject | Re: The meaning of xt in Forth-94 |
| Message-ID | <3fd5dbda-7e2b-4593-94cf-e1ef9ce1c0a6@googlegroups.com> |
| In reply to | #40109 |
duminică, 28 iunie 2015, 22:10:26 UTC+3, Rod Pemberton a scris:
> On Wed, 24 Jun 2015 12:54:07 -0400, Raimond Dragomir
> <raimond.dragomir@gmail.com> wrote:
>
> > I just tested a lot of combinations. But my system - I admit - has some
> > differences:
> > 1. I don't have POSTPONE
> > 2. I don't have [COMPILE]
> > 3. I don't have [ and ] - there is no way in my system to turn on and off
> > the state just like that. It's really ugly and I'm pretty sure this
> > confuses
> > a lot of programmers. Me for sure.
> > 4. I'm also not very sure if my COMPILE and COMPILE, are exactly the same
> > as the standard ones.
> >
> > What I have:
> > COMPILE
> > which parses the next word and compiles it. It is for compiling
> > immediate words. Normal words are compiled directly, and we need a way to
> > compile immediate words too (otherwise they get executed not compiled)
> >
> > COMPILE,
> > which is a normal word. It expects an xt on the stack, and compiles it
> > but when the word where it is compiled is executed. With COMPILE, we can
> > write words that are able to compile something on their turn.
> >
> > EVAL_XT
> > This word, and an entire familiy of words like it with constant folding
> > functionality, is a state smart word. It does COMPILE, in compiling mode
> > and EXECUTE in interpretation mode.
> >
>
> If you have a threaded, interpreted Forth, then COMPILE, is just , (comma).
>
> : COMPILE, , ;
> : [COMPILE] ' , ; immediate
>
My COMPILE, seems to be standard. It's not comma however, at least in my
current implementation. My system is a kind of token threaded implementation
with tokens being regular native functions with RET ending (no NEXT) and
all the other definitions being compiled with CALL opcodes (not native
calls, token calls). I also have STC implementations, basically the same
system without the primitives token table, simpler, faster but ... bigger
code generated (and non-portable between my windows box, BBB, cubie board
and Cortex-M embedded platforms...).
My COMPILE seems to be [COMPILE]. However, in my system COMPILE is a better
name, because I don't have [] words: I have immediate state smart ' (tick),
and not two variants of tick (' and [']) for example. Works very well although
I have to write "compile '" instead of just ' when I want to compile tick...
> POSTPONE is usually built with COMPILE and COMPILE, or , (comma) with the
> beginning similar to ' (tick). See this post of mine from a few years ago
> where I repeat a bunch of the c.l.f. definitions for POSTPONE over the
> years.
> You may need to scroll down a bit:
>
Thank you Rod, it was kind of mystery this POSTPONE to me...
So, I understand that POSTPONE compiles normally an immediate word (like
my COMPILE), and compiles code to compile a normal word.
So, POSTPONE IF will compile IF and POSTPONE DUP will compile something like
' DUP COMPILE, ?
Why I would need that?
There are two different actions. If I want code to compile DUP I can write
POSTPONE DUP, but if I want code to compile IF what can I write? POSTPONE IF
doesn't compile code that compiles IF, it compiles IF directly...
In my system I purposely left a lot of compiling words out of the kernel
in order to write them in high level definitions just to test that all meta-
compiling is working. I have high level CONSTANT, FIELD, ENUM, VARIABLE,
1,2,3 dimensional arrays, ." etc along with constant folding optimized versions
of a lot of words...
All I needed was COMPILE, COMPILE and EVAL_XT
> https://groups.google.com/forum/#!msg/comp.lang.forth/RqN6h4qNlPs/RrktBeS62cUJ
>
> So, now, you should just be missing [ and ] hopefully.
>
Hopefully :D
I will never implement [ and ] ever.
In fact [ and ] are taken, they are the quotations begin/end. B-)
>
> Rod Pemberton
>
> --
> Tolerance and socialism attracts intolerance and terrorism. See:
> France, United Kingdom, Germany, Denmark, Belgium, Netherlands, ...
[toc] | [prev] | [next] | [standalone]
| From | "Elizabeth D. Rather" <erather@forth.com> |
|---|---|
| Date | 2015-06-28 21:37 -1000 |
| Subject | Re: The meaning of xt in Forth-94 |
| Message-ID | <17qdncrL4Mk2aA3InZ2dnUU7-cudnZ2d@supernews.com> |
| In reply to | #40115 |
On 6/28/15 8:32 PM, Raimond Dragomir wrote: ... > So, I understand that POSTPONE compiles normally an immediate word (like > my COMPILE), and compiles code to compile a normal word. > So, POSTPONE IF will compile IF and POSTPONE DUP will compile something like > ' DUP COMPILE, ? > Why I would need that? > There are two different actions. If I want code to compile DUP I can write > POSTPONE DUP, but if I want code to compile IF what can I write? POSTPONE IF > doesn't compile code that compiles IF, it compiles IF directly... The usefulness of POSTPONE is that you don't need to know if the word you're POSTPONEing is immediate or not. During the development of Forth94 it became apparent that there was great diversity among systems as to the need for IMMEDIAcy. As one of the major objectives of Fort94 was to consolidate practice, we came up with this method of making compiler directives that didn't rely on the IMMEDIATE flag. Thus, : ?IF ( -- orig ) POSTPONE ?DUP POSTPONE IF ; IMMEDIATE Cheers, Eizabeth -- ================================================== Elizabeth D. Rather (US & Canada) 800-55-FORTH FORTH Inc. +1 310.999.6784 5959 West Century Blvd. Suite 700 Los Angeles, CA 90045 http://www.forth.com "Forth-based products and Services for real-time applications since 1973." ==================================================
[toc] | [prev] | [next] | [standalone]
| From | Raimond Dragomir <raimond.dragomir@gmail.com> |
|---|---|
| Date | 2015-06-29 01:38 -0700 |
| Subject | Re: The meaning of xt in Forth-94 |
| Message-ID | <969ba0af-f165-4e1a-92e1-98315d524604@googlegroups.com> |
| In reply to | #40116 |
luni, 29 iunie 2015, 10:37:16 UTC+3, Elizabeth D. Rather a scris:
> On 6/28/15 8:32 PM, Raimond Dragomir wrote:
> ...
> > So, I understand that POSTPONE compiles normally an immediate word (like
> > my COMPILE), and compiles code to compile a normal word.
> > So, POSTPONE IF will compile IF and POSTPONE DUP will compile something like
> > ' DUP COMPILE, ?
> > Why I would need that?
> > There are two different actions. If I want code to compile DUP I can write
> > POSTPONE DUP, but if I want code to compile IF what can I write? POSTPONE IF
> > doesn't compile code that compiles IF, it compiles IF directly...
>
> The usefulness of POSTPONE is that you don't need to know if the word
> you're POSTPONEing is immediate or not. During the development of
> Forth94 it became apparent that there was great diversity among systems
> as to the need for IMMEDIAcy. As one of the major objectives of Fort94
> was to consolidate practice, we came up with this method of making
> compiler directives that didn't rely on the IMMEDIATE flag.
>
> Thus,
>
> : ?IF ( -- orig ) POSTPONE ?DUP POSTPONE IF ; IMMEDIATE
>
Hmm.. yeah, pretty elegant.
In my systems this would be:
idef ?if \ -- orig
' ?dup compile,
compile if ;
Still not sure if I want postpone... It hides in a single name two things
quite different.
[toc] | [prev] | [next] | [standalone]
| From | Mark Wills <markwills1970@gmail.com> |
|---|---|
| Date | 2015-06-24 08:53 -0700 |
| Subject | Re: The meaning of xt in Forth-94 |
| Message-ID | <4ec533b4-e42e-42b2-93f9-25d1ad00c89c@googlegroups.com> |
| In reply to | #40020 |
On Wednesday, 24 June 2015 15:05:42 UTC+1, Raimond Dragomir wrote: > > > > In a typical state-smart word, ticking and compiling the word > > will lead to the interpretation semantics being executed > > when that word is eventually executed. However, that might > > not be the behaviour that you want. And there be the crux of > > the problem. > > > > Mark > > I understand very well the crux of the problem, what I don't understand is > why should it be so complicated. Because it's not. Yes, there are two > different execution semantics for S". When you execute it in interpretation > mode, it delivers the adr len of some buffer. When you execute what you > compiled, it delivers the adr len of the compiled copy in the code. > Yes, there are two words if you want, but they are dispatched by state, > in a single state smart word. What's so complicated? Is the state smartness > the problem? > > In my view, state smartness is quite simple. My system is a very simple one, > with state smart words and immediate flags. If you understand what is > all about, you can do whatever you want. For a S" type of a word, you should > recognize the fact that you need two "words", the rest is trivial. I don't > think it's a language deficiency. Not easy? Yes, not very easy for a regular > application programmer, more for a system programmer. > > Maybe S" given as an example here is too simple, maybe there are cases > more complicated. But I don't see how another sofistication with multiple > XTs could simplify a system based on state smart words and immediacy. Oh I'm in FULL agreement with you! It's a very simple problem. Just factor your definition into separate definitions, and write a state-smart "wrapper". Then, you can individually tick any of the words and do whatever you want. That's what I do. The complexity arises because the standard describes words in terms of the semantics (interpretation, compilation, and execution). It really is no more complex than this: (repeating what I wrote a few days back): Customer: "Ere... When I tick S" and compile it I get the interpretation behaviour. How can I get the compilation behaviour?" Support: "Tick (S")" Customer: "Oh. Thanks." Support: "You're welcome."
[toc] | [prev] | [next] | [standalone]
| From | "Rod Pemberton" <boo@fasdfrewar.cdm> |
|---|---|
| Date | 2015-06-24 20:08 -0400 |
| Subject | Re: The meaning of xt in Forth-94 |
| Message-ID | <op.x0ren1ibyfako5@localhost> |
| In reply to | #40012 |
On Wed, 24 Jun 2015 05:08:07 -0400, Mark Wills <markwills1970@gmail.com> wrote: > On Tuesday, 23 June 2015 23:13:28 UTC+1, Rod Pemberton wrote: >> You're indicating possible >> multiple XTs, which could be done too. > > Yes. That's what I'm advocating. But those XTs would actually > be the XTs of other words defined in the dictionary. By doing > this: > > * Factoring of different semantics into different words is > enforced; > * Each word has exactly one XT and one XT only. > > Simple. > This is sort of like the sub-words issue, e.g., (DO) to implement compile behavior for DO , (LOOP) for LOOP , (FIND) for FIND etc. > Here's an example: S" > Ok. You suggested an implementation. Now, I'm not a "Forth guy", but I'd think that another word, similar to CREATE or :NONAME , which provides extra dictionary fields for multiple XTs, one for each mode, would be needed or useful. E.g., perhaps CREATEXTS (create-xt-s). You would also probably need a flag on the word to indicate that it has multiple XTs, e.g., like IMMEDIATE sets a flag in the classic implementation, so that the word is handled properly. Rod Pemberton -- It's time to put an end to gun violence! Use a hammer ...
[toc] | [prev] | [next] | [standalone]
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2015-06-23 10:30 +0000 |
| Subject | Re: The meaning of xt in Forth-94 |
| Message-ID | <2015Jun23.123030@mips.complang.tuwien.ac.at> |
| In reply to | #39983 |
Raimond Dragomir <raimond.dragomir@gmail.com> writes:
>A name token would be a good solution, but I certainly want=20
>a tick that is optimized and fast and not derived from a name token with
>some other navigation after.
You seem to be unaware of the various costs involved in ': First, the
text interpreter has to parse, find and execute ', then ' itself has
to parse and find the ticked word, and finally has to do
NAME>INTERPRET (the "navigation after"). Let's do some benchmarking
(with gforth-fast-0.7.0):
perfex /nfs/nfstmp/anton/xxxgforthtest/c8/gcc-4.2.0/install/bin/gforth-fast-0.7.0 -e ': x 10000000 00 do S" '\'' dup" evaluate drop loop ; x bye'
This loop takes 2820 cycles per iteration on a Core 2 Duo (Wolfdale):
perfex /nfs/nfstmp/anton/xxxgforthtest/c8/gcc-4.2.0/install/bin/gforth-fast-0.7.0 -e ': x 100000000 0 do [ s" dup" find-name ]l name>int drop loop ; x bye'
This loop takes 205 cycles per iteration. That's surprisingly much,
but still only 7% of the time taken by processing "' DUP".
Why does NAME>INT take so much time? The Gforth 0.7.0 header
structure suffers from feature creep: ALIAS, COMPILE-ONLY, and
INTERPRET/COMPILE: are all reflected with some conditional processing
plus some surrounding code.
Here's data from a relatively recent Gforth version on a Core i3 (Ivy
Bridge):
2751 cycles per iteration for the first benchmark, 57 cycles per
iteration for the second one.
The ALIAS and COMPILE-ONLY conditionals are still present, and the
INTERPRET/COMPILE: stuff is covered in some other way (which might be
elegant, if it was understandable).
It's interesting that all this work is necessary, even for a word like
dup, although one of the central ideas of the new header design is to
use the xt as nt.
- 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 2015: http://www.mpeforth.com/euroforth2015/euroforth2015.htm
[toc] | [prev] | [next] | [standalone]
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Date | 2015-06-23 22:58 +0200 |
| Subject | Re: The meaning of xt in Forth-94 |
| Message-ID | <mmch7a$kbq$1@dont-email.me> |
| In reply to | #39986 |
Anton Ertl wrote:
> The ALIAS and COMPILE-ONLY conditionals are still present, and the
> INTERPRET/COMPILE: stuff is covered in some other way (which might be
> elegant, if it was understandable).
Here's a commented version:
: i/c>int ( nt -- xt ) @ ;
: i/c>comp ( nt -- xt1 xt2 ) cell+ @ ['] execute ;
: interpret/compile: ( interp-xt comp-xt "name" -- ) \ gforth
Header reveal
['] on vtcopy \ vtable template from normal colon definition
['] i/c>int set->int \ special name>interpret method
['] i/c>comp set->comp \ special name>compile method
swap , , ;
The new header structure has a vtable for each word, which defines methods
for COMPILE, TO targets (invoked by TO or IS), NAME>INTERPRET, NAME>COMPILE,
DEFER@, and POSTPONE targets (invoked by POSTPONE). While for each current
word you can modify its vtable, identical vtables (very common) are stored
only once.
NAME>INTERPRET and NAME>COMPILE need only be different for
interpret/compile: and synonyms/aliases; and at the moment, synonyms and
aliases still use a flag instead of a custom NAME>INTERPRET and
NAME>COMPILE. Also, COMPILE-ONLY and IMMEDIATE could be implemented more
elegantly as
: compile-only [: drop ['] compile-only-error ;] set->int ;
: immediate ['] execute set->comp ;
getting rid of the flags altogether.
The problem with changing these things is that several separate parts, like
the cross compiler, the decompiler and the compiler itself need to have a
common understanding, so I can't change too many things at once.
--
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 | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Date | 2015-06-23 23:49 +0200 |
| Subject | Re: The meaning of xt in Forth-94 |
| Message-ID | <mmck7g$unh$1@dont-email.me> |
| In reply to | #40003 |
Bernd Paysan wrote: > Also, COMPILE-ONLY and IMMEDIATE could be implemented more > elegantly as > > : compile-only [: drop ['] compile-only-error ;] set->int ; > : immediate ['] execute set->comp ; > > getting rid of the flags altogether. Actually, it should be : immediate [: name>interpret ['] execute ;] set->comp ; That should work with aliases, too; IIRC, the reason why I didn't yet remove those flags was that I haven't found a clean solution how to make an alias immediate without having to special-case immediate for that. This should do it. -- 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 | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Date | 2015-06-19 15:07 +0200 |
| Message-ID | <mm143n$6ft$1@dont-email.me> |
| In reply to | #39867 |
Anton Ertl wrote: > Somehow I think that Gforth's error message is more helpful > (unfortunately, it is not as helpful in the current development > version), and that it is also more helpful to report the error right > away rather than much later, potentially in a different context, which > may be (as in this case) confusing. Ok, fixed that, now the error message is more helpful: defer endif immediate :1: warning: redefined ENDIF with endif ok ' then is endif :2: error: Cannot tick compile-only word (try COMP' ... DROP) ' >>>then<<< is endif Backtrace: $7F261A57DBE8 throw $7F261A57EA70 name?int comp' then drop is endif ok : test if ." hello" endif ; ok true test hello ok false test ok see test : test IF s\" hello" type THEN ; ok Note that for copying semantics like that, SYNONYM was standardized. -- 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 | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2015-06-20 16:09 +0000 |
| Message-ID | <2015Jun20.180918@mips.complang.tuwien.ac.at> |
| In reply to | #39870 |
Bernd Paysan <bernd.paysan@gmx.de> writes:
>Note that for copying semantics like that, SYNONYM was standardized.
But you cannot use DEFER! (or IS) on a SYNONYM of THEN and get a
portable result. Extended example:
defer endif immediate
' then is endif
: foo if ." hello" endif ;
variable pre-endif
variable post-endif
:noname ]] 1 pre-endif +! then 1 post-endif +! [[ ; is endif
\ standardizing ]] ... [[ is left as an exercise to the reader.
: bar if ." hello" endif ;
- 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 2015: http://www.mpeforth.com/euroforth2015/euroforth2015.htm
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2015-06-22 16:24 -0700 |
| Message-ID | <ccf1992d-9379-451a-a377-6c68d907de6b@googlegroups.com> |
| In reply to | #39757 |
On Sunday, June 14, 2015 at 6:38:47 PM UTC-7, Michael Barry wrote: > On Sunday, June 14, 2015 at 6:53:21 AM UTC-7, Rod Pemberton wrote: > > [...] ... Have you tried a Forth forum > > where no one knows of you? Here, I'll help you with a plan > > of attack: > > > > Step 1) Help the NEWBs for a year or two to build up your cachet. > > Step 2) Pronounce ANS to be dead. The NEWBs won't know any better. > > Step 3) Declare your Forth to be the way of the future and provide > > some straw man arguments or other logical fallacies to prove it to > > them. They simply can't tell the difference. You're great at this > > form of misdirection. Like politics, an outrageous lie is the power > > backing all great leaders. > > Step 4) Convince your minions to go forth and spread the new prophecy. > > Step 5) Once the outside world partakes, claim your vindication. > > > > Wait. Did I mix that up? > > > > I'm not entirely sure (feigned), but those might just be the > > directions for building a cult or resurrecting Nazism ... The hallmark of a cult is to declare itself to be the standard. I'm not the one declaring myself to be standard, so I'm not building a cult. I'm okay with people doing their own thing. I wouldn't mind ANS-Forth if it was just presented as being yet-another Forth implementation --- declaring it to be the standard, especially without testing it in a reference compiler or getting any input from the Forth community, was offensive though. > I have been in private contact with Hugh regarding his project, > and it looks really promising (at least through a n00b's eyes). > I am not at liberty to discuss it, but I thought that I would > share just that small tidbit. Well, I posted my design publicly --- so you and Mark are at liberty to discuss it now if you want to. http://www.forth.org/FMITE.txt It is here: http://www.forth.org/literature.html With this description: This article describes a 16-bit Forth processor called FMITE that could be built into an FPGA. It is designed to have compact machine-code. It has support for quotations (a kind of lambda function), which Forth-200x lacks. Forth-200x's failure to support quotations makes it obsolete before it is even out the gate. My design is much more realistic to gain traction in the real world among people who understand computer-science concepts. Michael Barry has helped me a lot with my grammar and spelling. Looking at that description above I notice that I should have used "that" rather than "which" --- unfortunately, he didn't proofread the description, or he would have caught the mistake --- whenever I'm left alone with a keyboard, trouble results...
[toc] | [prev] | [next] | [standalone]
| From | "WJ" <w_a_x_man@yahoo.com> |
|---|---|
| Date | 2015-06-15 17:41 +0000 |
| Message-ID | <mln2nn$l5d$1@dont-email.me> |
| In reply to | #39735 |
Rod Pemberton wrote:
> Since I already know C is the "god language", why would
> I'm not entirely sure (feigned), but those might just be the
Let's try to read between the lines.
Gauche Scheme:
(define words (string-split
"Since I already know C is the \"god language\", why would
I'm not entirely sure (feigned), but those might just be the"
#/[\s"]+/))
(let1 i 3
(string-join
(map
(^(op n) (set! i (op i n)) (~ words i))
(list - * * -)
(lrange 2))))
===>
"I know I'm god"
[toc] | [prev] | [next] | [standalone]
| From | "WJ" <w_a_x_man@yahoo.com> |
|---|---|
| Date | 2015-06-15 16:54 +0000 |
| Message-ID | <mlmvvg$9g5$1@dont-email.me> |
| In reply to | #39717 |
Rod Pemberton wrote: > He must've gotten bored with Ms. Rather. > s/disambiguifiers/"is-not-an-actual-word-Hugh..." This pitiful wretch complains that "disambiguifiers" is not a word, but he meekly accepts "Ms.". Another who willingly licks the spittle of the cultural Marxists. -- "A woman's place is in the home." --- Wise old saying
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-06-15 22:57 -0400 |
| Message-ID | <mlo390$ftb$3@dont-email.me> |
| In reply to | #39761 |
On 6/15/2015 12:54 PM, WJ wrote: > Rod Pemberton wrote: > > >> He must've gotten bored with Ms. Rather. > >> s/disambiguifiers/"is-not-an-actual-word-Hugh..." > > This pitiful wretch complains that "disambiguifiers" is not a word, > but he meekly accepts "Ms.". > > Another who willingly licks the spittle of the cultural Marxists. We were talking so much about Hugh and I guess WJ got a little jealous... I wonder who left the gate open again at the nut house? -- Rick
[toc] | [prev] | [next] | [standalone]
| From | stephen@mpeforth.com (Stephen Pelc) |
|---|---|
| Date | 2015-06-13 10:51 +0000 |
| Message-ID | <557c0989.201972029@news.eternal-september.org> |
| In reply to | #39710 |
On Fri, 12 Jun 2015 18:40:17 -0700 (PDT), hughaguilar96@gmail.com wrote: >, can you explain why your SYNONYM wasn't written in ANS-Forth? --- as a me= >mber of the Forth-200x standards committee, can you tell of any purpose for= > a language standard other than portability of code? Because the action of SYNONYM is very implementation-dependent. I discussed this with several implementers. That there is one system on which SYNONYM can be written in ANS Forth does not disprove the need. You have been told this many times before, but you seem to have a desire for repetition. >Obviously this paper won't be in EuroForth --- Anton Ertl decides what gets= > in EuroForth, If you worked hard enough to buy an airline ticket to come to EuroForth, you might be surprised. Have you finished your Forth yet? Stephen -- Stephen Pelc, stephenXXX@mpeforth.com MicroProcessor Engineering Ltd - More Real, Less Time 133 Hill Lane, Southampton SO15 5AF, England tel: +44 (0)23 8063 1441, fax: +44 (0)23 8033 9691 web: http://www.mpeforth.com - free VFX Forth downloads
[toc] | [prev] | [next] | [standalone]
| From | "Alex McDonald" <blog@rivadpm.com> |
|---|---|
| Date | 2015-06-13 12:57 +0100 |
| Message-ID | <mlh5p5$6v7$1@dont-email.me> |
| In reply to | #39719 |
on 13/06/2015 11:51:21, wrote: > If you worked hard enough to buy an airline ticket to come to > EuroForth, you might be surprised. I'd be surprised.
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2015-06-13 21:53 -0700 |
| Message-ID | <81f8414b-bd50-49d9-aaf6-46911ba4a20f@googlegroups.com> |
| In reply to | #39719 |
On Saturday, June 13, 2015 at 3:51:20 AM UTC-7, Stephen Pelc wrote: > On Fri, 12 Jun 2015 18:40:17 -0700 (PDT), hughaguilar96@gmail.com > wrote: > > >, can you explain why your SYNONYM wasn't written in ANS-Forth? --- as a me= > >mber of the Forth-200x standards committee, can you tell of any purpose for= > > a language standard other than portability of code? > > Because the action of SYNONYM is very implementation-dependent. > I discussed this with several implementers. That there is one > system on which SYNONYM can be written in ANS Forth does not > disprove the need. My SYNONYM SYNONYM-FAST and ALIAS work on all ANS-Forth systems (I've tested it on VFX and gForth, but it should work on any compiler that conforms to ANS-Forth, specifically to section 4.1.2. of the document, which is where the sabotage is). My disambiguifiers disambiguify all ANS-Forth systems. This includes both VFX and gForth, despite the fact that VFX and gForth special-case the special words differently (VFX special-cases them in COMPILE, and gForth special-cases them in FIND). The ambiguity is sabotage that was artificially imposed on ANS-Forth --- ambiguity is not inherent in Forth. My disambiguifiers get rid of the ambiguity in all ANS-Forth systems across the board --- this is because only FIND but not POSTPONE is sabotaged in section 4.1.2. in the ANS-Forth document, so by using POSTPONE on every special-case word I totally work around the sabotage of FIND. Also btw, your SYNONYM has a bug in it. If you make a synonym of a word that was originally defined with CREATE and then you use >BODY on the synonym you won't get the body-address of the original word --- my ALIAS handles this situation correctly. > You have been told this many times before, but you seem to have > a desire for repetition. You ANS-Forth cult members are totally lying when you claim that there is some valid reason why FIND can't return an xt for dozens of words in the standard. The reason for this (invalid by my estimation) was to prevent cross-compilers from being written using ANS-Forth compilers --- the ANS-Forth compiler-writer (Anton Ertl) wants to be able to explain that his compiler is ANS-Forth compliant despite the fact that FIND fails on dozens of words in the standard --- this is clearly sabotage. You don't like the repetition because you don't enjoy lying --- I'm not going to drop the subject --- you are going to have to tell the same lie over and over again, even as it becomes increasingly obvious that you are lying. > >Obviously this paper won't be in EuroForth --- Anton Ertl decides what gets= > > in EuroForth, > > If you worked hard enough to buy an airline ticket to come to > EuroForth, you might be surprised. That is baloney -- Anton Ertl wrote gForth in such a way that FIND would abort on all of those special-case words --- he is truly guilty of sabotage. Anton Ertl won't acknowledge the fact that ANS-Forth can be disambiguified --- Anton Ertl won't acknowledge that I am a Forth programmer at all --- Anton Ertl is totally focused on keeping his job as the Forth-200x chairperson, which means that he is totally focused on doing what his boss Leon Wagner tells him to do. By comparison, you wrote VFX so that FIND provided an xt for the special-case words, but the xt can't be executed so it is not a valid "execution token". You also prevent an outer-interpreter from being written, because during interpretation mode (STATE is false) the outer-interpreter needs to give the xt to EXECUTE, and your EXECUTE will abort because it has been sabotaged. You won't acknowledge the fact that ANS-Forth can be disambiguified --- you won't acknowledge that I am a Forth programmer at all Both yourself and Anton Ertl have sabotage your respective compilers to prevent outer-interpreters from being written --- the difference is that you sabotaged EXECUTE to abort on some words and he sabotaged FIND to abort on some words. > Have you finished your Forth yet? I have a cross-compiler written in VFX --- it is pretty much just MFX ported from UR/Forth and retargeted for a different micro-controller --- it actually uses the built-in outer-interpreter rather than a custom outer-interpreter, but now that I know how to disambiguify ANS-Forth to allow a custom outer-interpreter to be written, I am rewriting it to use a custom outer-interpreter. Why do you ask? Do you expect me to email you the source-code? I'd be happy to do so --- the day after you email me the source-code for VFX --- oh wait, these are both closed-source commercial products, so that isn't going to happen. BTW: Using the built-in outer-interpreter works reasonably well. The major problem with this is that numbers don't work in compilation mode. For example: TARG : TEST ( -- 123 ) 123 ; This doesn't work because the 123 gets compiled into the host-computer memory rather than the target-computer memory. By comparison: TARG : TEST ( -- 123 ) [ 123 ] LITERAL ; This does work because LITERAL was defined as an immediate word in HOST mode and consequently it executes on the host-computer but works on target-computer memory. In MFX I had a short-hand version to help reduce source-code bloat: TARG : TEST ( -- 123 ) [ 123 ]L ; This is still somewhat ugly, but it was acceptable at Testra. It wasn't a big deal because they mostly used constants rather than raw numbers anyway. Also, they were building a Forth processor on a Lattice isp1048 PLD, which is difficult to do --- they weren't concerned about such a trivial issue as this --- so long as MFX had all the major features of a Forth cross-compiler, they were happy. This isn't really acceptable for a commercial cross-compiler though, which is why I'm rewriting the cross-compiler to use a custom outer-interpreter --- now that I have figured out how to disambiguify ANS-Forth to allow custom outer-interpreters to be written.
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2015-06-13 22:41 -0700 |
| Message-ID | <c6a0eff5-a0ea-440a-ab13-710baafb198e@googlegroups.com> |
| In reply to | #39719 |
On Saturday, June 13, 2015 at 3:51:20 AM UTC-7, Stephen Pelc wrote:
> On Fri, 12 Jun 2015 18:40:17 -0700 (PDT), hughaguilar96@gmail.com
> wrote:
>
> >, can you explain why your SYNONYM wasn't written in ANS-Forth? --- as a me=
> >mber of the Forth-200x standards committee, can you tell of any purpose for=
> > a language standard other than portability of code?
>
> Because the action of SYNONYM is very implementation-dependent.
> I discussed this with several implementers. That there is one
> system on which SYNONYM can be written in ANS Forth does not
> disprove the need.
My SYNONYM SYNONYM-FAST and ALIAS work on all ANS-Forth systems (I've tested it on VFX and gForth, but it should work on any compiler that conforms to ANS-Forth, specifically to section 4.1.2. of the document, which is where the sabotage is).
My disambiguifiers disambiguify all ANS-Forth systems. This includes both VFX and gForth, despite the fact that VFX and gForth special-case the special words differently (VFX special-cases them in COMPILE, and gForth special-cases them in FIND). The ambiguity is sabotage that was artificially imposed on ANS-Forth --- ambiguity is not inherent in Forth. My disambiguifiers get rid of the ambiguity in all ANS-Forth systems across the board --- this is because only FIND but not POSTPONE is sabotaged in section 4.1.2. in the ANS-Forth document, so by using POSTPONE on every special-case word I totally work around the sabotage of FIND.
Also btw, your SYNONYM has a bug in it. If you make a synonym of a word that was originally defined with CREATE and then you use >BODY on the synonym you won't get the body-address of the original word --- my ALIAS handles this situation correctly.
> You have been told this many times before, but you seem to have
> a desire for repetition.
You ANS-Forth cult members are totally lying when you claim that there is some valid reason why FIND can't return an xt for dozens of words in the standard. The reason for this (invalid by my estimation) was to prevent cross-compilers from being written using ANS-Forth compilers --- the ANS-Forth compiler-writer (Anton Ertl) wants to be able to explain that his compiler is ANS-Forth compliant despite the fact that FIND fails on dozens of words in the standard --- this is clearly sabotage.
You don't like the repetition because you don't enjoy lying --- I'm not going to drop the subject --- you are going to have to tell the same lie over and over again, even as it becomes increasingly obvious that you are lying.
> >Obviously this paper won't be in EuroForth --- Anton Ertl decides what gets=
> > in EuroForth,
>
> If you worked hard enough to buy an airline ticket to come to
> EuroForth, you might be surprised.
That is baloney -- Anton Ertl wrote gForth in such a way that FIND would abort on all of those special-case words --- he is truly guilty of sabotage. Anton Ertl won't acknowledge the fact that ANS-Forth can be disambiguified --- Anton Ertl won't acknowledge that I am a Forth programmer at all --- Anton Ertl is totally focused on keeping his job as the Forth-200x chairperson, which means that he is totally focused on doing what his boss Leon Wagner tells him to do.
By comparison, you wrote VFX so that FIND provided an xt for the special-case words, but the xt can't be executed so it is not a valid "execution token". This doesn't prevent an outer-interpreter from being written, because these are all words that don't have intepretation semantics so they shouldn't be given to EXECUTE by the outer-interpreter anyway. Weirdly enough, some of these words are non-immediate (IF) and some are immediate (;), although all of them would have been immediate in a traditional Forth. The immediate ones do have to be given to EXECUTE by the outer-interpreter, but this seems to work:
c" ;" find ok-2
.s
DATA STACK
top
1 0000:0001
5062384 004D:3EF0
ok-2
: my-; [ ' ; ] literal execute ; immediate ok-2
: ttt ." hello" my-; ok-2
ttt hello ok-2
So you are not preventing VFX users in writing a cross-compiler --- but you are okay with Anton Ertl preventing gForth users from writing a cross-compiler --- but it doesn't matter anyway, as my disambiguifiers work around the sabotage.
> Have you finished your Forth yet?
I have a cross-compiler written in VFX --- it is pretty much just MFX ported from UR/Forth and retargeted for a different micro-controller --- it actually uses the built-in outer-interpreter rather than a custom outer-interpreter, but now that I know how to disambiguify ANS-Forth to allow a custom outer-interpreter to be written, I am rewriting it to use a custom outer-interpreter.
Why do you ask? Do you expect me to email you the source-code? I'd be happy to do so --- the day after you email me the source-code for VFX --- oh wait, these are both closed-source commercial products, so that isn't going to happen.
BTW: Using the built-in outer-interpreter works reasonably well. The major problem with this is that numbers don't work in compilation mode. For example:
TARG
: TEST ( -- 123 ) 123 ;
This doesn't work because the 123 gets compiled into the host-computer memory rather than the target-computer memory. By comparison:
TARG
: TEST ( -- 123 ) [ 123 ] LITERAL ;
This does work because LITERAL was defined as an immediate word in HOST mode and consequently it executes on the host-computer but works on target-computer memory.
In MFX I had a short-hand version to help reduce source-code bloat:
TARG
: TEST ( -- 123 ) [ 123 ]L ;
This is still somewhat ugly, but it was acceptable at Testra. It wasn't a big deal because they mostly used constants rather than raw numbers anyway. Also, they were building a Forth processor on a Lattice isp1048 PLD, which is difficult to do --- they weren't concerned about such a trivial issue as this --- so long as MFX had all the major features of a Forth cross-compiler, they were happy.
This isn't really acceptable for a commercial cross-compiler though, which is why I'm rewriting the cross-compiler to use a custom outer-interpreter --- now that I have figured out how to disambiguify ANS-Forth to allow custom outer-interpreters to be written.
[toc] | [prev] | [next] | [standalone]
| From | stephen@mpeforth.com (Stephen Pelc) |
|---|---|
| Date | 2015-06-14 11:42 +0000 |
| Message-ID | <557d6684.291311275@news.eternal-september.org> |
| In reply to | #39730 |
On Sat, 13 Jun 2015 22:41:09 -0700 (PDT), hughaguilar96@gmail.com wrote: >Also btw, your SYNONYM has a bug in it. If you make a synonym of a word tha= >t was originally defined with CREATE and then you use >BODY on the synonym = >you won't get the body-address of the original word --- my ALIAS handles th= >is situation correctly.=20 VFX Forth for Windows IA32 © MicroProcessor Engineering Ltd, 1998-2015 Version: 4.72 [build 3538] Build date: 11 June 2015 Free dictionary = 7550062 bytes [7373kb] create foo 5 , 6 , ok synonym poo foo ok ' poo >body @ . 5 ok foo .dword 004C:ABC0 ok ' poo >body .dword 004C:ABC0 ok No bug to be seen. Stephen -- Stephen Pelc, stephenXXX@mpeforth.com MicroProcessor Engineering Ltd - More Real, Less Time 133 Hill Lane, Southampton SO15 5AF, England tel: +44 (0)23 8063 1441, fax: +44 (0)23 8033 9691 web: http://www.mpeforth.com - free VFX Forth downloads
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2015-06-14 09:26 -0700 |
| Message-ID | <4c83bf4f-cdd3-4c21-aac0-4dac17690f8c@googlegroups.com> |
| In reply to | #39733 |
On Sunday, June 14, 2015 at 4:42:48 AM UTC-7, Stephen Pelc wrote: > On Sat, 13 Jun 2015 22:41:09 -0700 (PDT), hughaguilar96@gmail.com > wrote: > > >Also btw, your SYNONYM has a bug in it. If you make a synonym of a word tha= > >t was originally defined with CREATE and then you use >BODY on the synonym = > >you won't get the body-address of the original word --- my ALIAS handles th= > >is situation correctly.=20 > > VFX Forth for Windows IA32 > © MicroProcessor Engineering Ltd, 1998-2015 > > Version: 4.72 [build 3538] > Build date: 11 June 2015 > > Free dictionary = 7550062 bytes [7373kb] > > create foo 5 , 6 , ok > synonym poo foo ok > ' poo >body @ . 5 ok > > foo .dword 004C:ABC0 ok > ' poo >body .dword 004C:ABC0 ok > > No bug to be seen. > > Stephen You are using VFX version 4.72 with a build-date of 3 days ago. This is the result I get: VFX Forth for Windows IA32 © MicroProcessor Engineering Ltd, 1998-2012 Version: 4.60 [build 3388] Build date: 24 October 2012 Free dictionary = 7562654 bytes [7385kb] create foo 5 , 6 , ok synonym poo foo ok ' poo >body @ . 5012107 ok ' foo >body @ . 5 ok locate synonym Definition found in /Kernel/Common/kernel.fth at line 5696. ok I couldn't find the Kernel/Common/ directory anywhere --- apparently it is not available in the evaluation version.
[toc] | [prev] | [next] | [standalone]
Page 17 of 26 — ← Prev page 1 … 15 16 [17] 18 19 … 26 Next page →
Back to top | Article view | comp.lang.forth
csiph-web