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 25 of 26 — ← Prev page 1 … 23 24 [25] 26 Next page →
| From | albert@spenarnc.xs4all.nl (Albert van der Horst) |
|---|---|
| Date | 2015-05-02 12:25 +0000 |
| Message-ID | <5544c223$0$21273$e4fe514c@dreader37.news.xs4all.nl> |
| In reply to | #38764 |
In article <26db7026-2dff-4f10-9799-24ec3d9d9078@googlegroups.com>,
JennyB <jennybrien@googlemail.com> wrote:
>On Friday, 1 May 2015 21:45:15 UTC+1, Bernd Paysan wrote:
>> Anton Ertl wrote:
>
>>
>> STATE-smart is just bad, no matter where you do it.
>>
>
>This, very much. So long as STATE is exposed, people will write STATE-smart
>words. Why not start by making STATE obsolescent? FORTH Inc. managed well
>enough without it. The user should never need to know what STATE the
>compiler is in. All they need know is that the Standard words perform the
>specified compilation semantics and that, if they need to, they can extend the
>compiler by specifying how it should deal with a particular definition.
May I add to that.
The user should at all time be aware what state the system is in.
If (s)he doesn't know whether Forth is compiling or interpreting,
(s)he is in bad shape.
The only question is whether we need STATE to inspect.
Now we are at that. Is IF a compile-only word, that cannot be
sensibly used during interpretation? Well, lets compile a piece
of ciforth code by hand.
First defeat the "compiler security", otherwise IF just says
ERROR! COMPILE-ONLY (by inspecting STATE!)
'NOOP '?COMP 3 CELLS MOVE.
Now define
: AAP 1 IF "WE GAAN NAAR ROME" TYPE THEN ;
OK
SEE AAP
: AAP
1
0BRANCH [ 50 , ] ( between TYPE (;) )
[ "WE GAAN NAAR ROME" ] DLITERAL TYPE
;
Now lets do this by hand, (using a shitload of carnal knowledge)
HERE 'AAP >DFA !
OK
'LIT , 1 , IF .S "WE GAAN NAAR ROME" 'LIT , , 'LIT , , 'TYPE , .S THEN '(;) ,
S[ 2 ]
S[ 2 ]
SEE AAP
: AAP
1
0BRANCH [ 50 , ] ( between TYPE (;) )
[ "WE GAAN NAAR ROME" ] DLITERAL TYPE
;
OK
In the above, you could replace
IF
by
'IF EXECUTE
and replace , by COMPILE, IF you so wish.
So the "interpretation semantics" of an immediate word, is its
semantics full stop. You can execute it in interpretation state or
in compilation state, whatever you choose. That is the meaning of
immediate. Make sure you know what you're doing.
>
>Abolish hypochondriac code!
Is the above an example of that? Or is that trying to gain insight in
what actually happens during compilation?
I can't say I'm very concerned about STATE. It turns smart words into
leaky abstractions, true. Forth is one pile of leaky abstractions anyway,
one more doesn't hurt. Piling well-thought-out abstractions from LISP
onto Forth and see it leak, if not bleed, doesn't make me happy.
A similar process is going on with c. It was a simple language, now
they are piling abstractions onto it, resulting in "miscompilations"
of what was transparent code before.
With all the attention to state smart word, I'd say that is one of the
least likely traps a novice (tm by Hugh) would fall in.
My most favorite feature of Forth is transparency.
Groetjes Albert
--
Albert van der Horst, UTRECHT,THE NETHERLANDS
Economic growth -- being exponential -- ultimately falters.
albert@spe&ar&c.xs4all.nl &=n http://home.hccnet.nl/a.w.m.van.der.horst
[toc] | [prev] | [next] | [standalone]
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2015-05-02 16:45 +0000 |
| Message-ID | <2015May2.184502@mips.complang.tuwien.ac.at> |
| In reply to | #38764 |
JennyB <jennybrien@googlemail.com> writes:
>On Friday, 1 May 2015 21:45:15 UTC+1, Bernd Paysan wrote:
>> Anton Ertl wrote:
>
>>
>> STATE-smart is just bad, no matter where you do it.
>>
>
>This, very much. So long as STATE is exposed, people will write STATE-smart
>words. Why not start by making STATE obsolescent?
I have much sympathy for that, but I think Bernd Paysan would not like
it, because it would break his traditional text interpreter.
Nevertheless, let us think about how a modern text interpreter without
STATE might look like:
For a single word, let's start out with a version that still has state:
parse-name find-name dup 0= -13 and throw
state @ if
name>compile
else
name>interpret
then
execute
Numbers etc. are handled with recognizers and thus are also covered by
FIND-NAME etc.
Now let's get rid of state:
defer name>x \ not the Gforth word of the same name
: ] ['] name>compile is name>x ;
: [ ['] name>interpret is name>x ;
\ and here the text interpreter:
parse-name find-name dup 0= -13 and throw name>x execute
Nicely concise.
- 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 | "Alex McDonald" <blog@rivadpm.com> |
|---|---|
| Date | 2015-05-02 19:12 +0100 |
| Message-ID | <mi340d$o2b$1@dont-email.me> |
| In reply to | #38781 |
on 02/05/2015 17:45:01, wrote: > JennyB <jennybrien@googlemail.com> writes: >>On Friday, 1 May 2015 21:45:15 UTC+1, Bernd Paysan wrote: >>> Anton Ertl wrote: >> >>> >>> STATE-smart is just bad, no matter where you do it. >>> >> >>This, very much. So long as STATE is exposed, people will write STATE-smart >>words. Why not start by making STATE obsolescent? > > I have much sympathy for that, but I think Bernd Paysan would not like > it, because it would break his traditional text interpreter. > > Nevertheless, let us think about how a modern text interpreter without > STATE might look like: > > For a single word, let's start out with a version that still has > state: > > parse-name find-name dup 0= -13 and throw > state @ if > name>compile > else > name>interpret > then > execute > > Numbers etc. are handled with recognizers and thus are also covered by > FIND-NAME etc. > > Now let's get rid of state: > > defer name>x \ not the Gforth word of the same name >: ] ['] name>compile is name>x ; >: [ ['] name>interpret is name>x ; : [ ['] name>interpret is name>x ; immediate > > \ and here the text interpreter: > parse-name find-name dup 0= -13 and throw name>x execute > > Nicely concise. Which is exactly how my Forth works (excepting the NAME>xxx words; they're named differently). > > - anton
[toc] | [prev] | [next] | [standalone]
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Date | 2015-05-03 16:23 +0000 |
| Message-ID | <2015May3.182339@mips.complang.tuwien.ac.at> |
| In reply to | #38757 |
Bernd Paysan <bernd.paysan@gmx.de> writes:
>Anton Ertl wrote:
>> I don't remember any surprises.
>
>Hm, just implement this
>
>: my' ( "name" -- xt ) bl word find 0= abort" not found" ;
>: [my'] ( "name -- ) \ runtime: ( -- xt )
> my' postpone literal ; immediate
>
>: test" [my'] s" execute type ;
>
>test" blabla"
>:7: error: Stack underflow
>test" >>>blabla<<<"
>
>WTF? Shouldn't that work? Works fine in interpretation state:
>
>my' s" execute blabla" type blabla ok
Yet nobody has complained about that, so apparently nobody was
surprised.
But yes, I am all for making FIND obsolescent and replacing it with a
word that is more fitting for the standard concepts, such as
FIND-NAME.
>> find-name ( c-addr u -- nt | 0 )
>>
>> No STATE-smartness there.
>
>FIND-NAME shows that having a single token is a good idea. The open
>question here is: Why must a new token type be introduced? Why not make it
>possible to use xt?
It is possible to use xt, it's just not required. We had this
discussion when TRAVERSE-WORDLIST was proposed, no need to rehash it
now.
>> It is a result of the Forth-94 goal that such words may be implemented
>> as immediate or non-immediate words (e.g., EXIT is implemented as
>> immediate compile-only, and UNLOOP is a normal word). We could have
>> implemented ' EXIT as producing an xt, but then ' EXIT EXECUTE would
>> have been equivalent to POSTPONE EXIT, unlike for UNLOOP; so you could
>> not use the xt portably, because the xt would reflect the
>> implementation.
>
>IMHO the problem here is immediacy, and the fact that an xt does not convey
>the information of immediacy. If we defined e.g.
>
>: IMMEDIATE ( -- )
> immediate-bit set-flags \ legacy for FIND
> ['] execute set-compiler ;
>
>the xt could still be used without knowledge of the internal working. Since
>these words have no interpretation semantics, EXECUTing them has no standard
>meaning, but COMPILE, could be used for both immediate and non-immediate
>versions.
All user-defined immediate words and all the words that the standard
specifies as immediate have interpretation semantics, and your
IMMEDIATE just does not behave as specified by the standard. If you
replace SET-COMPILER with SET-COMPSEM, I think it would be correct. I
think one could implement the immediate-flag check of FIND by testing
whether the compsem field contains the xt of COMPILE,.
As for having an EXIT with an xt that cannot be EXECUTEd but can be
COMPILE,d, what's would that be good for? Why not just pass the
compilation token around and EXECUTE that?
>> Anyway, I see no direct connection to dual-xt. You can implement
>> ticking of such words on dual-xt systems, and you can implement an
>> error on ticking such words on single-xt systems.
>
>my' exit >name .name compile-only-error ok
>: test [my'] exit >name .name ; ok
>test EXIT ok
>
>EXIT appears to be a dual-xt word in Gforth... at least for FIND.
And yet the implementation of EXIT has only a single xt (plus
immediate and compile-only flags). If you don't like this behaviour
of FIND, there are also other options:
* FIND reports not-found when called in interpretation state; I would
find the resulting error message confusing, though.
* FIND ignores the compile-only flag and treats EXIT just as an
immediate word. A text interpreter based on that FIND would not
report an error if it encounters EXIT in interpretation state.
>>>The relation of name to xt is complex, and complex is bad
>>
>> It reflects the complexity of the concepts in the standard. If you
>> have two semantics (interpretation and compilation semantics), which
>> may be arbitrarily unrelated, you need two reifications of them: the
>> execution toklen (for interpretation/execution semantics), and the
>> compilation token (for compilation semantics).
>
>"need" in mathematical terms is something that can't be done without. IMHO
>you either need two tokens, *or* you need to ways to deal with the single
>token. The SET-COMPILER COMPILE, ultimatively (when implemented with full
>consequence) provides a way to deal with the two semantics even when there's
>only one token.
>
>> The relation is as simple as the words NAME>INTERPRET and NAME>COMPILE
>> that are already in the standard.
>
>That's an abstraction over multiple possible ways to deal with that problem
>now. The question is: do we need the abstraction? If we implemented SET-
>COMPILER consequently,
>
>: name>interpret ( nt -- xt ) name> ;
>: name>compile ( nt -- xt1 xt2 ) name> ['] compile, ;
>
>with a simple NAME> could do the job.
But you could no longer do what Stephen Pelc calls "interp-compile,",
and you could not use all xts for use2. You would have introduced two
kinds of xts: Those that can be used for use 2 (full xts), and those
that cannot (use-2-incompatible xts). Is that simplicity? Not in my
book.
>> If we want it simpler, let us get rid of the two unrelated semantics;
>> then we can return to single-xt-with-immediate (and maybe
>> compile-only) flags.
>
>Getting rid of the two unrelated semantics IMHO is wishful thinking.
I think it is doable, but you may be right that there will always be
programmers who will want to go in that direction, and use whatever
tools appear to give them that, however broken the results, such as
STATE or SET-COMPILER. So it may be better to give them a proper tool
for the job, such as SET-COMPSEM.
>> In any case, in every Forth except VFX, use 2 works with all xts you
>> can get, including the non-standard cases. I'll deal with your ;S
>> example below.
>
>The problem with that is that your definition of "xts you can get" only
>applies to ', not to FIND. And it doesn't work for the xts you can get with
>FIND.
No, it also works with all xts you can get with FIND. The only system
with a broken COMPILE, is VFX.
>>>The SET-COMPILER definition of COMPILE, is pretty straight-forward:
>>>"perform the compilation semantics associated with xt".
>>
>> That makes no sense, if you claim that we cannot get at the xt.
>
>You can get every xt, if not with ', then with FIND. Writing a MY' that
>solves the "get the xt" problem is trivial, see above.
If we can get at the xt, COMPILE, should work correctly for it. Then
implementing S" etc. with SET-COMPILER is a bug.
Somehow your arguments are contradictory: First you argue that we
cannot get at the xt of S", so we won't notice if COMPILE, does not
work correctly for it, and therefore using SET-COMPILER is acceptable.
Now you argue that we can get at the xt after all. In that case the
VFX implementation of S" is buggy.
>>>Doesn't matter, there are a number of words that are compile-only by
>>>having no meaningful interpretation semantics, and users can for sure
>>>write such words which have no meaningful interpretation semantics.
>>
>> In any case, for now they don't have a standard means to write words
>> for which use 2 does not work.
>
>That's a "burying the tools" failure.
It's a failure to let existing code continue to work?
>> Both test1 and test2 report a -14 error (on VFX), so this use 2 case
>> works correctly even on VFX. I see no failure here.
>
>The failure here is rather that the user's intention (create a compile-only
>word) doesn't work. The problem is that the standard has such words, but
>the user can't create them, so you have a burrying the tools issue here.
>That should not be the case. The user should have the same capabilities of
>defining words as the system programmer has.
Fine with me. Gforth gives them COMPILE-ONLY and INTERPRET/COMPILE:
etc. for that. If you don't like the existing dual-semantics words,
SET-COMPSEM might be an interface you like better.
>>>If you define your user-defined STATE-smart S" replacement, you can tick
>>>and postpone S", and you get portable results (i.e. your replacement
>>>behaves the same way on all three systems, though it's a way you don't
>>>like).
>>
>> Yes. It works for use 1 and use 2.
>
>No, because it's state smart. It just copies the state-smart behavior.
Yes, but it still works for both use 1 and use 2 as specified.
>> yes, VFX as currently implemented is not
>> use-2-compatible, but there is no reason to keep it that way. If we
>> see all current implementations as unchangeable, we don't need to talk
>> about tightening the standard.
>>
>> Here's how VFX could change in a world where we only have
>> single-xt+immediate(+compile-only) words and use2 works universally:
>> Every word is tickable, and immediate-compile-only words provide a the
>> xt that, when EXECUTEd, performs the compilation semantics. IF would
>> be such a word. The system's text interpreter checks for compile-only
>> and reports an error if such a word is interpreted;
>
>I see an urge to duplicate Gforth's FIND behavior on these words, to provide
>error reporting in user-written text interpreters...
>
>> newly written
>> user-defined text interpreters would also check for that (we would
>> provide a way to check for that). Old user-written text interpreters
>> would not report an error when interpreting IF; not a big issue IMO.
>
>So you suggest to break old user-written text interpreters, because it's IYO
>not a big issue, and you usually don't write your own text interpreters?
>Maybe it's an issue, and you just don't know it.
You mean there are programs out there that rely on getting a
compile-only error when they pass a compile-only word to a
user-written text interpreter? I doubt it, and in any case these
programs are not standard and would not work on, e.g., SwiftForth (for
which I have not seen any indication of any compile-only check at
all).
But if you really have the urge to have a Gforth-like FIND, why did
you give that as example of surprising behaviour earlier in your
posting?
Anyway, you don't want to go for single-xt+immediate+compile-only
anyway, so let's drop that.
>>>The point here is that your equivalence doesn't even hold for a simple
>>>word
>>>like ;S. It's not state-smart.
>>
>> The equivalence does hold. The problem is that ;S consumes the return
>> address,
>
>I've explaind it already, don't dodge this: The reason for EXIT (and it's
>primitive friend ;S) is compile-only is that it consumes the return address.
>In Gforth's text interpreter, where ;S simply works:
>
>." foo" ;s ." bar" foo ok
>
>there's no reason to make it compile-only.
So ;S is not compile-only, contrary to your claim. The reason why
EXIT is compile-only is that it is not implemented as a word with
default compilation semantics (unlike ;S), but as a compiling word.
>However, it's also
>possible to have an OOF where the much-wanted use 2 works even with VFX.
>Just define
>
>: :: ( object "name" -- ) >vt @ postpone literal postpone execute ;
>
>instead of
>
>: :: ( object "name" -- ) >vt @ compile, ;
I certainly won't slow down my OOP system on all systems just to work
around a bug in VFX. The workaround should be targetted at VFX, i.e.,
[defined] vfxforth [if]
: compile, postpone literal postpone execute ;
[then]
This does not fix VFX completely, because then use 1 of COMPILE, does
not work. I guess VFX as currently implemented is hopeless.
- 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-05-03 15:47 -0700 |
| Message-ID | <6e8abb05-76d7-4467-b5bd-6458a7bb86f3@googlegroups.com> |
| In reply to | #38795 |
On Sunday, May 3, 2015 at 10:41:05 AM UTC-7, Anton Ertl wrote:
> ...I am all for making FIND obsolescent and replacing it with a
> word that is more fitting for the standard concepts, such as
> FIND-NAME.
So, all the legacy code that has been written since Forth was invented in the 1970s will cease to work --- this is so you can have a "word that is more fitting for the standard concepts" --- maybe later a doctor with a flashlight can show us where you got these "standard concepts" which nobody ever heard of until now.
Anyway, I can defeat you with my disambiguifiers:
: if state @ 0= abort" *** no interpretation semantics for: IF ***"
postpone if ; immediate
[toc] | [prev] | [next] | [standalone]
| From | Jan Coombs <Jan-54 <jenfhaomndgfwutc@murmic.plus.com>> |
|---|---|
| Date | 2015-05-04 10:11 +0100 |
| Message-ID | <20150504101128.51af59cd@T60A> |
| In reply to | #38803 |
On Sun, 3 May 2015 15:47:05 -0700 (PDT) hughaguilar96@gmail.com wrote: > On Sunday, May 3, 2015 at 10:41:05 AM UTC-7, > Anton Ertl wrote: > > ...I am all for making FIND obsolescent and > > replacing it with a word that is more fitting > > for the standard concepts, such as FIND-NAME. > > So, all the legacy code that has been written > since Forth was invented in the 1970s will > cease to work --- No, 'obsolecent' is a change in direction marker, so you can fine the new faster route, not the entrance to a blind alley. Jan Coombs.
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2015-05-04 09:16 -0700 |
| Message-ID | <1073a4d5-07e1-4b6d-a746-47cd910cb719@googlegroups.com> |
| In reply to | #38808 |
On Monday, May 4, 2015 at 2:11:29 AM UTC-7, Jan Coombs wrote: > On Sun, 3 May 2015 15:47:05 -0700 (PDT) > hughaguilar96@gmail.com wrote: > > > On Sunday, May 3, 2015 at 10:41:05 AM UTC-7, > > Anton Ertl wrote: > > > ...I am all for making FIND obsolescent and > > > replacing it with a word that is more fitting > > > for the standard concepts, such as FIND-NAME. > > > > So, all the legacy code that has been written > > since Forth was invented in the 1970s will > > cease to work --- > > No, 'obsolecent' is a change in direction marker, > so you can fine the new faster route, not the > entrance to a blind alley. > > Jan Coombs. Will the old FIND actually work, or will it be the cripple-ware version that aborts on some of the ANS-Forth standard words? Why not just give us a FIND that works on all words in the dictionary? How obvious would that be? Also, why not define words such as IF etc. to be immediate? Even if Stephen Pelc wants to do the special-casing in COMPILE, (reasonable in an analytic compiler), he can still make IF etc. immediate using my disambiguifier so that it meets the requirement of the standard --- it is easy to turn a non-immediate word into an immediate word using standard Forth code (my disambiguifiers are all ANS-Forth), but turning an immediate word into a non-immediate requires delving into the guts of COMPILE, to special-case them there, which is highly non-standard.
[toc] | [prev] | [next] | [standalone]
| From | roman.pavlyuk.0@gmail.com |
|---|---|
| Date | 2015-05-04 10:15 -0700 |
| Message-ID | <6d70f311-3fac-47c9-b3a2-f3983b5dfeb9@googlegroups.com> |
| In reply to | #38808 |
> > No, 'obsolecent' is a change in direction marker, > so you can fine the new faster route, not the > entrance to a blind alley. > > Jan Coombs. Cyan words in ColorForth seem to be the answer to all this discussion ;)
[toc] | [prev] | [next] | [standalone]
| From | "WJ" <w_a_x_man@yahoo.com> |
|---|---|
| Date | 2015-06-15 23:35 +0000 |
| Message-ID | <mlnngn$gp1$1@dont-email.me> |
| In reply to | #37787 |
Bernd Paysan wrote:
> The failure here is rather that the user's intention (create a
> compile-only word) doesn't work. The problem is that the
> standard has such words, but the user can't create them, so
> you have a burrying the tools issue here. That should not be
> the case. The user should have the same capabilities of
> defining words as the system programmer has.
Anton Ertl wrote:
> As long as we only have those few words, rarely a problem (and that
> problem is covered in the standard by disallowing ticking these words).
Bernd Paysan wrote:
> These problems are all holes of the needlessly complicated model of the
> current standard.
Bernd Paysan wrote:
> Your problem was that you had a wrong mental model of how
> Forth compilation works, caused by the ANS Forth standard.
Bernd Paysan wrote:
> You have fully bought the ANS Forth semantics stuff, the rest
> of the Forth world didn't.
Let's try to summarize using an ingenious algorithm
that comes with Gauche Scheme:
Function: lcs seq-a seq-b :optional eq-fn
Calculates and returns the longest common sequence of two
lists, seq-a and seq-b. Optional eq-fn specifies the
comparison predicate; if omitted, equal? is used.
(lcs '(x a b y) '(p a q b))
===> (a b)
(use util.lcs) ;; longest common subsequence
(define (get-words text) (remove #/^$/ (string-split text #/\W+/)))
(define a (get-words
"As long as we only have those few words, rarely a problem (and
that problem is covered in the standard by disallowing ticking
these words)."))
(define b (get-words
"Your problem was that you had a wrong mental model of how
Forth compilation works, caused by the ANS Forth standard."))
(lcs a b
(lambda words
(or
(find (^(pair) (every (cut member <> pair) words))
'(("Your" "a") ("was" "is")))
(apply equal? words))))
===>
("a" "problem" "is" "the" "standard")
[toc] | [prev] | [next] | [standalone]
| From | Ching-Tang Tseng <ilikeforth@gmail.com> |
|---|---|
| Date | 2015-07-02 02:31 -0700 |
| Message-ID | <02145133-e546-4483-a941-44f9acbd064f@googlegroups.com> |
| In reply to | #37787 |
When I am posting, box of this topic show me 410 posts, 2108 views, huge numbers ARE saying something. This topic is "bug in VFX --- IF doesn't work" posted by Hugh. I support Hugh's opinion and don't like C-based gFooth's doing. Current FORTH community needs such a person like Hugh to point out C-based production's problem. I read Hugh's posting and need these kinds of opinion. These opinions let me don't have to waste time to touch poor FORTH system or its poor area. Other topic opinion can create new thread, I suggest with sorry and please. It will make me more easy to use "Mark all as read" to ignore some meaningless topics. Everybody is welcome to ignore my posting. I will post as less as I can. Ching
[toc] | [prev] | [next] | [standalone]
| From | stephen@mpeforth.com (Stephen Pelc) |
|---|---|
| Date | 2015-07-02 17:20 +0000 |
| Message-ID | <559571e1.96609001@news.eternal-september.org> |
| In reply to | #40237 |
On Thu, 2 Jul 2015 02:31:09 -0700 (PDT), Ching-Tang Tseng <ilikeforth@gmail.com> wrote: >When I am posting, box of this topic show me 410 posts, 2108 views, huge nu= >mbers ARE saying something. This topic is "bug in VFX --- IF doesn't work" = >posted by Hugh. IF in VFX Forth *does* work. It just doesn't behave in the way he wants. >I support Hugh's opinion and don't like C-based gFooth's do= >ing. Current FORTH community needs such a person like Hugh to point out C-b= >ased production's problem. There is no C in VFX, except in the support and parser DLLs. The Forth kernel is cross-compiled by a cross-compiler hosted by VFX Forth. The rest of the code is then compiled by the kernel. However, his initial assertion is just wrong. There are occasions when Hugh talks sense, but in the main he lacks any social grace. 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 | Ching-Tang Tseng <ilikeforth@gmail.com> |
|---|---|
| Date | 2015-07-02 15:40 -0700 |
| Message-ID | <952e0708-94fa-4f3f-94b2-453d6e5bd1a4@googlegroups.com> |
| In reply to | #37787 |
Stephen, Thanks for reply. I know "IF in VFX Forth *does* work. It just doesn't behave in the way he wants." I am usually use FORTH 83 standard only. Say it frankly, any other kind of the following standard, ANS FORTH included, to me is just a REFERENCE MANUAL only. I don't care. Hugh pointed out something for STANDARD is right. In fact, nobody has said anything to REFERENCE MANUAL, isn't it? Hugh cares STANDARD, Hugh can say. My English is poor, so I said nothing. Otherwise, I will say more. I said in Chinese a lot about FORTH STANDARD and posted it out on web for a long period of time already. Chinese FORTH users read my articles. I had encouraged Hugh stop to say something to FORTH Inc. He seems accepted my suggestion a little. I think Hugh as a good friend. I like to talk FORTH techniques with him and support him many opinions in FORTH. I know VFX is not a C-based FORTH also. I have downloaded VFX evaluation version in my computer. I am too old and for nothing to buy a normal VFX system. To extend out an ABC FORTH in VFX is a good idea, but I have no intention for the present. I will not waste my time on a FORTH system without source code, at least I should not develop the application under a situation have to INCLUDE many files to compile it every time. I used to use FORTH meta-compiler to fix my development. I believe VFX is a good FORTH system, and the same as all other have called .dll system, suffered difficulties to call .dll in Win64 environment. Then for many years we don't have Win64 FORTH system in public domain. FORTH community should concern this point in my personal opinion. Any way, I wish I will have the chance to do something on VFX in the future. Ching
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-07-02 19:55 -0400 |
| Message-ID | <mn4iu5$f6m$1@dont-email.me> |
| In reply to | #40258 |
On 7/2/2015 6:40 PM, Ching-Tang Tseng wrote: > Stephen, > > Thanks for reply. > > I know "IF in VFX Forth *does* work. It just doesn't behave in the way he wants." > > I am usually use FORTH 83 standard only. Say it frankly, any other kind of the following standard, ANS FORTH included, to me is just a REFERENCE MANUAL only. I don't care. Hugh pointed out something for STANDARD is right. In fact, nobody has said anything to REFERENCE MANUAL, isn't it? Hugh cares STANDARD, Hugh can say. My English is poor, so I said nothing. Otherwise, I will say more. I said in Chinese a lot about FORTH STANDARD and posted it out on web for a long period of time already. Chinese FORTH users read my articles. > > I had encouraged Hugh stop to say something to FORTH Inc. He seems accepted my suggestion a little. I think Hugh as a good friend. I like to talk FORTH techniques with him and support him many opinions in FORTH. > > I know VFX is not a C-based FORTH also. I have downloaded VFX evaluation version in my computer. I am too old and for nothing to buy a normal VFX system. To extend out an ABC FORTH in VFX is a good idea, but I have no intention for the present. I will not waste my time on a FORTH system without source code, at least I should not develop the application under a situation have to INCLUDE many files to compile it every time. I used to use FORTH meta-compiler to fix my development. > > I believe VFX is a good FORTH system, and the same as all other have called .dll system, suffered difficulties to call .dll in Win64 environment. Then for many years we don't have Win64 FORTH system in public domain. FORTH community should concern this point in my personal opinion. > > Any way, I wish I will have the chance to do something on VFX in the future.. If you and Hugh are friends that is good. Hugh doesn't have many friends here because he likes to be rude and argumentative, even downright offensive. So he can use a friend. Be aware that some of his posts here cross a line that most rational people won't cross. I think he even made an inexcusable comment about a potential deadly incident one of our posters had been in. But that was a while back and I don't remember the details. Just be aware that supporting him in anything having to do with Forth Inc can have ramifications that you may not know about. This is an area where Hugh gives all indications of being mentally unbalanced and I fear that someday he may do something violent. If you have read all his posts here for the last few years you should have seen this. I'm not worried about you, I am worried that Hugh may do something to someone that he has irrational anger toward. So be careful what you support him in. -- Rick
[toc] | [prev] | [next] | [standalone]
| From | Ching-Tang Tseng <ilikeforth@gmail.com> |
|---|---|
| Date | 2015-07-02 19:43 -0700 |
| Message-ID | <0bd4c691-0321-4aac-bf30-e663b1180159@googlegroups.com> |
| In reply to | #37787 |
Rick, OK. That will be fine. If anybody doesn't like me to use VFX, I will never to touch it. It belongs to your company not mine, and I can advice all my friend don't waste their time on it as well. There are so many FORTH systems in our world today, even in case no FORTH system can be use; we know how to build one out for ourselves. Fortunately, Win32Forth is still over there now, we will never hurt by the C-based Forth system. I prefer to say many thanks to all Win32Forth system contributors. I told Hugh he has one paper in the last one volume FORTH DIMENSIONS, 1999. I give respects to all FORTH contributors, he is the one. He can talk everything to me if he likes. We have never had any problem between us. I am able to identify what's wrong and what's right in all posted message. I can not say Hugh is 100% right, but almost most are right. I support. That is enough. So called cross a line is defined by a person. Most of the angry are created by both sides. In Chinese thinking, we'd better don't to stimulate others first, can prevent angry happened. I wish all visitors here can understand this simple regulation. I respect Hugh, Hugh respects me, and everything is peaceful. Hugh supported me off here sometimes. Then I gave him some special FORTH message. In Chinese we said it is communicated with politeness. For example, Win32Forth is always been reported has virus by AVS as one new thread here, I am able to give Hugh which one function calling make it happen and gave him my real testing code if he likes. If somebody make me angry here, I will post as less as I can. I did not lose anything. I like Hugh be my friend. Ching
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-07-02 23:08 -0400 |
| Message-ID | <mn4u8v$c2q$1@dont-email.me> |
| In reply to | #40260 |
On 7/2/2015 10:43 PM, Ching-Tang Tseng wrote: > Rick, > > OK. That will be fine. If anybody doesn't like me to use VFX, I will > never to touch it. It belongs to your company not mine, and I can > advice all my friend don't waste their time on it as well. I have no idea what you are talking about. VFX is not mine and I never said anything about it. Are you responding to someone else? > There are > so many FORTH systems in our world today, even in case no FORTH > system can be use; we know how to build one out for ourselves. > Fortunately, Win32Forth is still over there now, we will never hurt > by the C-based Forth system. I prefer to say many thanks to all > Win32Forth system contributors. Some of this is not clear, I expect it is the language barrier. > So called cross a line is defined by a person. Most of the angry are > created by both sides. In Chinese thinking, we'd better don't to > stimulate others first, can prevent angry happened. I wish all > visitors here can understand this simple regulation. I respect Hugh, > Hugh respects me, and everything is peaceful. If you are reading Hugh's posts in this group for the last year or so and feel that he has been provoked into saying all of the things he has said, you are a poor judge of character. I don't really care, but everyone here knows Hugh is pretty much off his nut (I hope that translates ok) and most try not to encourage his rants. > Hugh supported me off here sometimes. Then I gave him some special > FORTH message. In Chinese we said it is communicated with politeness. > For example, Win32Forth is always been reported has virus by AVS as > one new thread here, I am able to give Hugh which one function > calling make it happen and gave him my real testing code if he likes. > If somebody make me angry here, I will post as less as I can. I did > not lose anything. If you really want to help, report to your AVS provider that it is generating a false positive with a valid program. This is not a problem to be fixed by changing the program. It should be fixed by changing the AVS software. > I like Hugh be my friend. If you are friends with Hugh, that is fine. But sooner or later I expect something will happen and he may no longer treat you as a friend. I hope you understand when he attacks others here that this is about Hugh and not the rest of the world. I'm done discussing Hugh. Enjoy forth and this group. :) -- Rick
[toc] | [prev] | [next] | [standalone]
| From | Ching-Tang Tseng <ilikeforth@gmail.com> |
|---|---|
| Date | 2015-07-02 21:56 -0700 |
| Message-ID | <77aa96bb-c6d2-4039-af37-0876515cbf0d@googlegroups.com> |
| In reply to | #37787 |
Rick, > I have no idea what you are talking about. VFX is not mine and I never > said anything about it. Are you responding to someone else? You response me with this following line first, so I think you are working in VFX company. - show quoted text - > Any way, I wish I will have the chance to do something on VFX in the future.. As to the following message I posted, it is just emphasize that I don't care anybody don't let me use their FORTH system. If you are not talking about VFX, then please ignore it. You said that > Just be aware that supporting him in anything having to do with Forth > Inc can have ramifications that you may not know about. Are you threatening me? (I make a joke only),I don't care even I knew it. If Forth Inc. can ramify me, please indicate me from Forth Inc. directly. I am able write Chinese articles to influence Forth Inc. back forever in Chinese environment. I gave respects to others first. I know how to do my response if negative thing occurred. > I'm done discussing Hugh. Enjoy forth and this group. :) Good and thanks, say it again: I like Hugh be my friend. > If you really want to help, report to your AVS provider that it is > generating a false positive with a valid program. This is not a problem > to be fixed by changing the program. It should be fixed by changing the > AVS software. Sorry, as I know, AVS is a free download system. They did this virus report is corrected in some aspects. AVS don't have to change anything. We should try to accept it spontaneously. For the purpose of stop everybody to attack Hugh. I post my personal study result here. Win32Forth call WriteConsoleA in d_TYPE ( addr cnt -- ), parameter transfer in Win32 before calling are put 4 data on the stack. The cnt means total string length. AVS thinks this kind of calling will be a virus. In my personal thinking it is right. If cnt is -1 or a huge number, terrible thing will happen in the system immediately. So, it makes WriteConsoleA as a virus. Make sense! I have done a test in Win64 environment as following: [OUTH] to rcx, ; OUTH means output console handle code addr of keycode to rdx, cnt to r8, ; cnt to be fixed as 1 dummy to r9 ; dummy means 0 call WriteConsoleA It is still can work, but to be reported virus by AVS as well. As to the rest, please think it by yourself. The question is: do I have to report such a condition to AVS Company? I think don't have to do. Ching
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2015-07-03 01:25 -0400 |
| Message-ID | <mn56ad$2o5$1@dont-email.me> |
| In reply to | #40264 |
On 7/3/2015 12:56 AM, Ching-Tang Tseng wrote: > Rick, > >> I have no idea what you are talking about. VFX is not mine and I >> never said anything about it. Are you responding to someone else? > > You response me with this following line first, so I think you are > working in VFX company. - show quoted text - >> Any way, I wish I will have the chance to do something on VFX in >> the future.. > As to the following message I posted, it is just emphasize that I > don't care anybody don't let me use their FORTH system. If you are > not talking about VFX, then please ignore it. That quote was from you and I was responding it. I did not write it. According to the messages I see, you wrote it. > You said that >> Just be aware that supporting him in anything having to do with >> Forth Inc can have ramifications that you may not know about. > > Are you threatening me? (I make a joke only),I don't care even I knew > it. If Forth Inc. can ramify me, please indicate me from Forth Inc. > directly. I am able write Chinese articles to influence Forth Inc. > back forever in Chinese environment. I gave respects to others first. > I know how to do my response if negative thing occurred. > >> I'm done discussing Hugh. Enjoy forth and this group. :) > > Good and thanks, say it again: I like Hugh be my friend. I don't understand everything you have written so I will only say this. My point is that I am concerned that Hugh may someday do something to hurt someone. I am hoping you don't say anything to him that he might interpret as encouraging that. Enough said, I am done discussing Hugh. >> If you really want to help, report to your AVS provider that it is >> generating a false positive with a valid program. This is not a >> problem to be fixed by changing the program. It should be fixed by >> changing the AVS software. > > Sorry, as I know, AVS is a free download system. They did this virus > report is corrected in some aspects. AVS don't have to change > anything. We should try to accept it spontaneously. > > For the purpose of stop everybody to attack Hugh. I post my personal > study result here. > > Win32Forth call WriteConsoleA in d_TYPE ( addr cnt -- ), parameter > transfer in Win32 before calling are put 4 data on the stack. The cnt > means total string length. AVS thinks this kind of calling will be a > virus. In my personal thinking it is right. If cnt is -1 or a huge > number, terrible thing will happen in the system immediately. So, it > makes WriteConsoleA as a virus. Make sense! > > I have done a test in Win64 environment as following: > > [OUTH] to rcx, ; OUTH means output console handle code addr of > keycode to rdx, cnt to r8, ; cnt to be fixed as 1 dummy to > r9 ; dummy means 0 call WriteConsoleA > > It is still can work, but to be reported virus by AVS as well. > > As to the rest, please think it by yourself. > > The question is: do I have to report such a condition to AVS Company? > I think don't have to do. I use AVS to mean Anti-Virus Software, not any specific AVS program. None of the facts you have posted about AVS and Win32Forth is relevant. Win32Forth is not a virus. Any AVS that reports that Win32Forth is a virus is mistaken. If the AVS company is informed about it they can fix their software. This is true for any AVS whether FOSS or commercial. I reported this to my AVS company and they fixed their software so it no longer is reported as a virus. That is why I suggest that others do the same. I'm done discussing the AVS problem. -- Rick
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2015-07-02 23:00 -0700 |
| Message-ID | <e3a32b81-0d3b-4a25-8803-123c800b930a@googlegroups.com> |
| In reply to | #40265 |
On Thursday, July 2, 2015 at 10:25:56 PM UTC-7, rickman wrote: > On 7/3/2015 12:56 AM, Ching-Tang Tseng wrote: > > You said that > >> Just be aware that supporting him in anything having to do with > >> Forth Inc can have ramifications that you may not know about. > > > > Are you threatening me? (I make a joke only),I don't care even I knew > > it. If Forth Inc. can ramify me, please indicate me from Forth Inc. > > directly. I am able write Chinese articles to influence Forth Inc. > > back forever in Chinese environment. I gave respects to others first. > > I know how to do my response if negative thing occurred. > > > >> I'm done discussing Hugh. Enjoy forth and this group. :) > > > > Good and thanks, say it again: I like Hugh be my friend. > > I don't understand everything you have written so I will only say this. > My point is that I am concerned that Hugh may someday do something to > hurt someone. I am hoping you don't say anything to him that he might > interpret as encouraging that. > > Enough said, I am done discussing Hugh. Hello Ching :-) Thanks for your support and friendship. I advise you to stop responding to Rickman --- he is a troll --- this is very loathsome behavior (even by comp.lang.forth's low standards) for him to accuse me of being a violent criminal. He says that he is done "discussing" me, then 2 hours later he does it again --- he has been doing this since 2009 --- he is going to continue making wild accusations so long as people continue responding to him.
[toc] | [prev] | [next] | [standalone]
| From | "Alex McDonald" <blog@rivadpm.com> |
|---|---|
| Date | 2015-07-03 22:25 +0100 |
| Message-ID | <mn6uhs$bco$1@dont-email.me> |
| In reply to | #40264 |
on 03/07/2015 05:56:24, Ching-Tang Tseng wrote: > > Win32Forth call WriteConsoleA in d_TYPE ( addr cnt -- ), parameter > transfer in Win32 before calling are put 4 data on the stack. The cnt > means total s tring length. AVS thinks this kind of calling will be a > virus. In my person al thinking it is right. If cnt is -1 or a huge > number, terrible thing will happen in the system immediately. So, it > makes WriteConsoleA as a virus. M ake sense! Only if WriteConsoleA (the ANSI version of WriteConsole) could be persuaded to write the supplied buffer to an area outside of a display buffer. It can't. The limit appears to be around 26000 characters. > > I have done a test in Win64 environment as following: > > [OUTH] to rcx, ; OUTH means output console handle code > addr of keycode to rdx, > cnt to r8, ; cnt to be fixed as 1 > dummy to r9 ; dummy means 0 > call WriteConsoleA > > It is still can work, but to be reported virus by AVS as well. Since this is exactly how C programs call WriteConsoleA -- there isn't any other way of doing it -- AVS should be reporting any programs that use WriteConsole as a virus too. Here's the parameter list; BOOL WINAPI WriteConsole( _In_ HANDLE hConsoleOutput, _In_ const VOID *lpBuffer, _In_ DWORD nNumberOfCharsToWrite, _Out_ LPDWORD lpNumberOfCharsWritten, _Reserved_ LPVOID lpReserved ); > The question is: do I have to report such a condition to AVS Company? > I thi nk don't have to do. No, that's true; but please don't stop others from doing so. I don't believe your analysis is correct btw.
[toc] | [prev] | [next] | [standalone]
| From | Ching-Tang Tseng <ilikeforth@gmail.com> |
|---|---|
| Date | 2015-07-03 00:50 -0700 |
| Message-ID | <da6e5316-0475-4bc5-a9da-ef5e550057d2@googlegroups.com> |
| In reply to | #37787 |
Hugh, I know you are always interesting about nuclear reactor facilities. This time let me tell you what's on a control panel we are always operated in the real nuclear reactor control room. There are three pushbuttons on the centre control panel: 1. The right side pushbutton is "TEST". When you push it down, all alarm indicator lights may be more than hundreds will flash up and honking up as well, no touch no response. 2. If any one abnormal thing happened in the reactor, control panel will alarm up. Operator on shift must understand what happened immediately, then push the left side pushbutton down means "ACKNOWLEDGED". Then he may have to take some response action to overcome the system problem. 3. Until every trouble things of all system had been treated done. We can push down the center pushbutton "RESET" means all troubles are over. Then all indicator lights are off and alarms are quiet back. Now I am pushing "acknowledged" button down. And I suggest you again not a word to anybody please, just talk FORTH technique. Ching
[toc] | [prev] | [next] | [standalone]
Page 25 of 26 — ← Prev page 1 … 23 24 [25] 26 Next page →
Back to top | Article view | comp.lang.forth
csiph-web