Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #37726 > unrolled thread
| Started by | albert@spenarnc.xs4all.nl (Albert van der Horst) |
|---|---|
| First post | 2015-03-29 12:43 +0000 |
| Last post | 2015-04-04 11:25 -0700 |
| Articles | 20 on this page of 80 — 21 participants |
Back to article view | Back to comp.lang.forth
Importing from wordlists. albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-03-29 12:43 +0000
Importing from wordlists. Mark Wills <markwills1970@gmail.com> - 2015-03-29 06:15 -0700
Re: Importing from wordlists. albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-03-29 15:11 +0000
Re: Importing from wordlists. hughaguilar96@gmail.com - 2015-03-29 09:14 -0700
Re: Importing from wordlists. albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-03-29 19:52 +0000
Re: Importing from wordlists. anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-03-30 12:39 +0000
Re: Importing from wordlists. Mark Wills <markwills1970@gmail.com> - 2015-03-30 09:09 -0700
Re: Importing from wordlists. stephen@mpeforth.com (Stephen Pelc) - 2015-03-30 16:42 +0000
Re: Importing from wordlists. hughaguilar96@gmail.com - 2015-03-30 17:55 -0700
Re: Importing from wordlists. Mark Wills <markwills1970@gmail.com> - 2015-04-02 05:41 -0700
Re: Importing from wordlists. "HAA" <someone@microsoft.com> - 2015-03-31 13:26 +1000
Re: Importing from wordlists. hughaguilar96@gmail.com - 2015-03-30 19:54 -0700
Re: Importing from wordlists. Mark Wills <markwills1970@gmail.com> - 2015-03-31 02:23 -0700
Re: Importing from wordlists. Lars Brinkhoff <lars.spam@nocrew.org> - 2015-03-31 12:02 +0200
Re: Importing from wordlists. Mark Wills <markwills1970@gmail.com> - 2015-03-31 07:41 -0700
Re: Importing from wordlists. "Alex McDonald" <blog@rivadpm.com> - 2015-03-31 16:36 +0100
Re: Importing from wordlists. albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-03-31 16:52 +0000
Re: Importing from wordlists. "Alex McDonald" <blog@rivadpm.com> - 2015-03-31 18:33 +0100
Re: Importing from wordlists. JennyB <jennybrien@googlemail.com> - 2015-03-31 15:25 -0700
Re: Importing from wordlists. albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-01 00:59 +0000
Re: Importing from wordlists. JennyB <jennybrien@googlemail.com> - 2015-04-01 08:05 -0700
Re: Importing from wordlists. albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-01 15:25 +0000
Re: Importing from wordlists. anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-01 15:58 +0000
Re: Importing from wordlists. "Alex McDonald" <blog@rivadpm.com> - 2015-04-01 15:57 +0100
Re: Importing from wordlists. Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-03-31 23:58 +0100
Re: Importing from wordlists. Bernd Paysan <bernd.paysan@gmx.de> - 2015-04-01 02:00 +0200
Re: Importing from wordlists. hughaguilar96@gmail.com - 2015-03-31 18:48 -0700
Re: Importing from wordlists. Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-04-01 08:03 +0100
Re: Importing from wordlists. Bernd Paysan <bernd.paysan@gmx.de> - 2015-04-01 16:38 +0200
Re: Importing from wordlists. "Alex McDonald" <blog@rivadpm.com> - 2015-04-01 15:54 +0100
Re: Importing from wordlists. Bernd Paysan <bernd.paysan@gmx.de> - 2015-04-01 17:41 +0200
Re: Importing from wordlists. Bernd Paysan <bernd.paysan@gmx.de> - 2015-04-01 18:24 +0200
Re: Importing from wordlists. Bernd Paysan <bernd.paysan@gmx.de> - 2015-04-02 05:27 +0200
Re: Importing from wordlists. Coos Haak <chforth@hccnet.nl> - 2015-04-02 12:38 +0200
Re: Importing from wordlists. "Alex McDonald" <blog@rivadpm.com> - 2015-04-02 15:45 +0100
Re: Importing from wordlists. "Alex McDonald" <blog@rivadpm.com> - 2015-04-02 17:25 +0100
Re: Importing from wordlists. Bernd Paysan <bernd.paysan@gmx.de> - 2015-04-03 02:00 +0200
Re: Importing from wordlists. Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-04-03 20:49 +0100
Re: Importing from wordlists. "Elizabeth D. Rather" <erather@forth.com> - 2015-04-03 11:08 -1000
Re: Importing from wordlists. Paul Rubin <no.email@nospam.invalid> - 2015-04-03 14:14 -0700
Re: Importing from wordlists. franck.bensusan@gmail.com - 2015-04-04 02:47 -0700
Re: Importing from wordlists. anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-03 21:37 +0000
Re: Importing from wordlists. "Elizabeth D. Rather" <erather@forth.com> - 2015-04-03 14:05 -1000
Re: Importing from wordlists. Bernd Paysan <bernd.paysan@gmx.de> - 2015-04-04 05:14 +0200
Re: Importing from wordlists. anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-04 14:07 +0000
Re: Importing from wordlists. Paul Rubin <no.email@nospam.invalid> - 2015-04-04 14:02 -0700
Re: Importing from wordlists. Melzzzzz <mel@zzzzz.com> - 2015-04-05 00:36 +0200
Re: Importing from wordlists. Hans-Peter Diettrich <DrDiettrich1@aol.com> - 2015-04-04 04:35 +0200
Re: Importing from wordlists. anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-04 13:30 +0000
Re: Importing from wordlists. albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-04 16:38 +0000
Re: Importing from wordlists. Hans-Peter Diettrich <DrDiettrich1@aol.com> - 2015-04-04 16:48 +0200
Re: Importing from wordlists. "Alex McDonald" <blog@rivadpm.com> - 2015-04-03 23:49 +0100
Re: Importing from wordlists. "Elizabeth D. Rather" <erather@forth.com> - 2015-04-03 14:09 -1000
Re: Importing from wordlists. "Alex McDonald" <blog@rivadpm.com> - 2015-04-04 20:30 +0100
Re: Importing from wordlists. hughaguilar96@gmail.com - 2015-04-04 13:29 -0700
Re: Importing from wordlists. Johan Kotlinski <kotlinski@gmail.com> - 2015-04-03 23:57 -0700
Re: Importing from wordlists. "Elizabeth D. Rather" <erather@forth.com> - 2015-04-03 21:35 -1000
Re: Importing from wordlists. krishna.myneni@ccreweb.org - 2015-04-04 10:00 -0700
Re: Importing from wordlists. Melzzzzz <mel@zzzzz.com> - 2015-04-04 19:08 +0200
Re: Importing from wordlists. Coos Haak <chforth@hccnet.nl> - 2015-04-02 22:45 +0200
Re: Importing from wordlists. Bernd Paysan <bernd.paysan@gmx.de> - 2015-04-03 02:08 +0200
Re: Importing from wordlists. Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-04-02 20:59 +0100
Re: Importing from wordlists. Bernd Paysan <bernd.paysan@gmx.de> - 2015-04-03 02:03 +0200
Re: Importing from wordlists. Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-04-03 20:52 +0100
Re: Importing from wordlists. Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-04-09 12:39 +0100
Re: Importing from wordlists. albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-01 15:03 +0000
Re: Importing from wordlists. albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-01 01:10 +0000
Re: Importing from wordlists. Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-04-01 07:32 +0100
Re: Importing from wordlists. anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-01 07:52 +0000
Re: Importing from wordlists. albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-01 10:39 +0000
SYNONYM (wase: Importing from wordlists.) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-01 11:29 +0000
Re: SYNONYM (wase: Importing from wordlists.) albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-01 15:08 +0000
Re: Importing from wordlists. "Alex McDonald" <blog@rivadpm.com> - 2015-04-01 15:49 +0100
Re: Importing from wordlists. anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-01 17:12 +0000
Re: Importing from wordlists. "Alex McDonald" <blog@rivadpm.com> - 2015-04-01 18:45 +0100
Re: Importing from wordlists. Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-04-01 20:43 +0100
Re: Importing from wordlists. mhx@iae.nl (Marcel Hendrix) - 2015-04-04 09:53 +0200
Re: Importing from wordlists. anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-04-04 14:20 +0000
Re: Importing from wordlists. albert@spenarnc.xs4all.nl (Albert van der Horst) - 2015-04-04 17:10 +0000
Re: Importing from wordlists. mhx@iae.nl - 2015-04-04 11:25 -0700
Page 2 of 4 — ← Prev page 1 [2] 3 4 Next page →
| From | JennyB <jennybrien@googlemail.com> |
|---|---|
| Date | 2015-04-01 08:05 -0700 |
| Message-ID | <18cc304f-b3d9-4056-8008-45cfa04743a9@googlegroups.com> |
| In reply to | #37792 |
On Wednesday, 1 April 2015 01:59:01 UTC+1, Albert van der Horst wrote:
> In article <866e5680-c68d-40e6-9c92-8c7768ab8faa@googlegroups.com>,
> JennyB <jennybrien@googlemail.com> wrote:
> >Remember that SYNONYM can create a synonym with the identical name (but
> >in a different wordlist) so in the OP's case you would do something like
> >
> > ALSO standard
> > SYNONYM ALIAS ALIAS
> > ...
> > PREVIOUS
>
> If I'm the OP you're talking about, let met try to pull this back on track.
>
> Define syntactic sugar ^H^H^H^H^ a macro like abbreviation for the above
> lines to make it convenient and usable,
> like so
> standard IMPORT ALIAS
>
Not easy. It means building a temporary string and then EVALUATEing that, which in turn means managing space for temporary buffers of unknown size.
At the last EuroForth Anton suggested a word
>STRING-EXECUTE \ xt -- addr u
Execute xt, diverting output to a temporary buffer.
Return the resulting string.
: .IMPORT ." SYNONYM " PARSE-NAME
2DUP TYPE SPACE TYPE SPACE ;
: IMPORT ['] .IMPORT >STRING-EXECUTE EVALUATE ;
Yes, ALIAS is the better building block, but since they are both system-defined words anyway, I'd prefer if it was made clear that they should be true aliases - that ', ['] and WORD should return the same value for both the original and the alias, and therefore any other parsing words should treat them exactly the same - so, for example
VALUE foo
SYNONYM bar foo
1 TO bar
would work as expected.
[toc] | [prev] | [next] | [standalone]
| From | albert@spenarnc.xs4all.nl (Albert van der Horst) |
|---|---|
| Date | 2015-04-01 15:25 +0000 |
| Message-ID | <551c0dd0$0$23223$e4fe514c@dreader34.news.xs4all.nl> |
| In reply to | #37811 |
In article <18cc304f-b3d9-4056-8008-45cfa04743a9@googlegroups.com>, JennyB <jennybrien@googlemail.com> wrote: >On Wednesday, 1 April 2015 01:59:01 UTC+1, Albert van der Horst wrote: >> In article <866e5680-c68d-40e6-9c92-8c7768ab8faa@googlegroups.com>, >> JennyB <jennybrien@googlemail.com> wrote: >> >Remember that SYNONYM can create a synonym with the identical name (but >> >in a different wordlist) so in the OP's case you would do something like >> > >> > ALSO standard >> > SYNONYM ALIAS ALIAS >> > ... >> > PREVIOUS >> >> If I'm the OP you're talking about, let met try to pull this back on track. >> >> Define syntactic sugar ^H^H^H^H^ a macro like abbreviation for the above >> lines to make it convenient and usable, >> like so >> standard IMPORT ALIAS >> >Not easy. It means building a temporary string and then EVALUATEing that, which in turn means managing space for temporary buffers of >unknown size. please limit your line size to 72 characters. > >At the last EuroForth Anton suggested a word > > >STRING-EXECUTE \ xt -- addr u > Execute xt, diverting output to a temporary buffer. > Return the resulting string. > > : .IMPORT ." SYNONYM " PARSE-NAME > 2DUP TYPE SPACE TYPE SPACE ; > > : IMPORT ['] .IMPORT >STRING-EXECUTE EVALUATE ; > Okay with string manipulation it is at least possible. I use format for that : IMPORT NAME 2DUP "synonym %s %s" FORMAT EVALUATE ( PREVIOUS) ; ( or FORMAT&EVAL ) >Yes, ALIAS is the better building block, but since they are both system-defined words anyway, I'd prefer if it was made clear that they >should be true aliases - that ', ['] and WORD should return the same value for both the original and the alias, and therefore any other >parsing words should treat them exactly the same - so, for example > > VALUE foo > SYNONYM bar foo > 1 TO bar > > would work as expected. Oops. VALUE foo 'foo ALIAS bar 1 TO bar works as expected in ciforth. But the execution tokens of foo and bar are not the same: 'foo ID. foo OK 'bar ID. bar OK I expect more Forths behave like this. -- 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-04-01 15:58 +0000 |
| Message-ID | <2015Apr1.175827@mips.complang.tuwien.ac.at> |
| In reply to | #37811 |
JennyB <jennybrien@googlemail.com> writes:
> >STRING-EXECUTE \ xt -- addr u=20
> Execute xt, diverting output to a temporary buffer. =20
> Return the resulting string.
>
> : .IMPORT ." SYNONYM " PARSE-NAME
> 2DUP TYPE SPACE TYPE SPACE ;
>
> : IMPORT ['] .IMPORT >STRING-EXECUTE EVALUATE ;
Hmm, the documentation of >STRING-EXECUTE in Gforth says:
: >string-execute ( ... xt -- ... addr u )
\G execute xt while the standard output (TYPE, EMIT, and everything
\G that uses them) is redirected to a string. The resulting string
\G is addr u, which is in ALLOCATEd memory; it is the
\G responsibility of the caller of >STRING-EXECUTE to FREE this
\G string.
Also, I would not want late binding of SYNONYM. So I would write this
as:
: imported ( c-addr u -- )
[: 2dup type space type ;] >string-execute over >r
['] synonym execute-parsing
r> free throw ;
: import ( "name" -- ) parse-name imported ;
- 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 2014: http://www.euroforth.org/ef14/
[toc] | [prev] | [next] | [standalone]
| From | "Alex McDonald" <blog@rivadpm.com> |
|---|---|
| Date | 2015-04-01 15:57 +0100 |
| Message-ID | <mfh0um$4lh$1@dont-email.me> |
| In reply to | #37788 |
on 31/03/2015 23:26:00, JennyB wrote: > Remember that SYNONYM can create a synonym with the identical name > (but in a different wordlist) so in the OP's case you would do > something like > > ALSO standard > SYNONYM ALIAS ALIAS > ... > PREVIOUS > > The portable version that makes a new colon definition works, but to > use CREATE you would need some input stream gymnastics to avoid having > the new word find itself. > PARSE-NAME and EXECUTE-PARSING will allow defering the CREATE until after the FIND.
[toc] | [prev] | [next] | [standalone]
| From | Gerry Jackson <gerry@jackson9000.fsnet.co.uk> |
|---|---|
| Date | 2015-03-31 23:58 +0100 |
| Message-ID | <mff8p3$q11$1@dont-email.me> |
| In reply to | #37784 |
On 31/03/2015 18:33, Alex McDonald wrote:
> on 31/03/2015 17:52:22, Albert wrote:
>> In article <0165a96b-3372-4a43-8e77-045994fb5934@googlegroups.com>,
>> Mark Wills <markwills1970@gmail.com> wrote:
>
>>>
>>>
>>> --BLOCK-00046---------
>>> : SYNONYM
>>> CREATE BL WORD FIND DUP IF
>>> SWAP , IMMEDIATE 1+ IF
>>> DOES> @ EXECUTE
>>> ELSE
>>> DOES> STATE @ IF
>>> @ ,
>>> ELSE
>>> @ EXECUTE
>>> THEN
>>> THEN
>>> ELSE
>>> TRUE ABORT" Word not found"
>>> THEN ;
>>
>> Oh boy.
>> I don't think it is worthwhile to define SYNONYM
>> pseudo portably. My comrade-in-arms Coos Haak
>> tried this one and it didn't work on his Forth
>> of r the test that has been snipped.
>> (The SYNONYM he implemented himself passed.)
>
> : synonym
> : bl word find
> >r compile, postpone ;
> r> 1+ if immediate then ;
>
> I think that should be pretty portable across ANS Forths. (I know, it
> uses the deprectated FIND.)
>
That doesn't meet the specification of SYNONYM.
15.6.2.2264 SYNONYM TOOLS EXT
( “<spaces>newname” “<spaces>oldname” – – )
For both strings skip leading space delimiters. Parse newname and
oldname delimited by a space. Create a definition for newname with
the semantics defined below. Newname may be the same as oldname;
when looking up oldname, newname shall not be found.
^^^^^^^^^^^^^^^^^^^^^^^^^^
e.g. on GForth
' DUP SYNONYM DUP DUP ' DUP . .' DUP SYNONYM DUP DUP ' DUP . .
redefined dup with DUP 2143110184 4268604 ok
although I must confess I don't know why that condition is there.
Also it doesn't allow a synonym of a deferred word to be reassigned, but
it could be argued that IS and DEFER! cannot be applied to a synonym of
a deferred word - but IMHO that ought to be possible (it is on VFX Forth
and my system).
--
Gerry
[toc] | [prev] | [next] | [standalone]
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Date | 2015-04-01 02:00 +0200 |
| Message-ID | <mffcdg$5u3$1@dont-email.me> |
| In reply to | #37789 |
Gerry Jackson wrote: > Also it doesn't allow a synonym of a deferred word to be reassigned, but > it could be argued that IS and DEFER! cannot be applied to a synonym of > a deferred word - but IMHO that ought to be possible (it is on VFX Forth > and my system). Gforth's git head SYNONYM makes a new header which behaves (apart from the name) really identical to the old one - IS and TO work on DEFER and VALUE, when you tick it, the xt is the same, and so on. A good SYNONYM implementation requires not only carnal knowledge, but some preparation in the system. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o ID: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* http://bernd-paysan.de/
[toc] | [prev] | [next] | [standalone]
| From | hughaguilar96@gmail.com |
|---|---|
| Date | 2015-03-31 18:48 -0700 |
| Message-ID | <e390c16a-1f0f-4355-af35-d1823c81fe48@googlegroups.com> |
| In reply to | #37791 |
On Tuesday, March 31, 2015 at 5:00:38 PM UTC-7, Bernd Paysan wrote: > Gerry Jackson wrote: > > > Also it doesn't allow a synonym of a deferred word to be reassigned, but > > it could be argued that IS and DEFER! cannot be applied to a synonym of > > a deferred word - but IMHO that ought to be possible (it is on VFX Forth > > and my system). > > Gforth's git head SYNONYM makes a new header which behaves (apart from the > name) really identical to the old one - IS and TO work on DEFER and VALUE, > when you tick it, the xt is the same, and so on. > > A good SYNONYM implementation requires not only carnal knowledge, but some > preparation in the system. IS uses >BODY --- anything that uses >BODY is going to be a problem, which is why I don't use >BODY at all --- in the novice-package I have VECTOR that is more efficient than DEFER and IS, and which does not use >BODY. I don't recommend VALUE and TO either --- in my language I won't have this cruft --- I will only have @ and ! for both global and local data. Anyway, you guys' definitions of SYNONYM aren't going to work anyway because of this bug: https://groups.google.com/forum/#!topic/comp.lang.forth/oXXQAGDKP7w If you are going to be ANS-Forth programmers, you to work around the bugs.
[toc] | [prev] | [next] | [standalone]
| From | Gerry Jackson <gerry@jackson9000.fsnet.co.uk> |
|---|---|
| Date | 2015-04-01 08:03 +0100 |
| Message-ID | <mfg55t$2s2$1@dont-email.me> |
| In reply to | #37791 |
On 01/04/2015 01:00, Bernd Paysan wrote: > Gforth's git head SYNONYM makes a new header which behaves (apart from the > name) really identical to the old one - IS and TO work on DEFER and VALUE, > when you tick it, the xt is the same, and so on. My system has headers separated from the body of a word, so implementation of SYNONYM was trivial. Incidentally I'm still using what is now a very old version of GForth, 0.7.0, which I believe was the last one for which a Windows executable was made available. Not everybody wants to compile from the latest source code in your repository - after all I primarily develop and use my own system. It would be better for GForth's image if a more recent version of GForth was made available as a Windows executable. -- Gerry
[toc] | [prev] | [next] | [standalone]
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Date | 2015-04-01 16:38 +0200 |
| Message-ID | <mfgvqo$vu4$1@dont-email.me> |
| In reply to | #37799 |
Gerry Jackson wrote: > Incidentally I'm still using what is now a very old version of GForth, > 0.7.0, which I believe was the last one for which a Windows executable > was made available. Not everybody wants to compile from the latest > source code in your repository - after all I primarily develop and use > my own system. It would be better for GForth's image if a more recent > version of GForth was made available as a Windows executable. Unfortunately, the Windows users are the ones who need the most care and give back the least ;-). I could try to build a recent snapshot, but really, we need a volunteer for that. Somebody who uses Windows for more than just the annual tax report... -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o ID: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* http://bernd-paysan.de/
[toc] | [prev] | [next] | [standalone]
| From | "Alex McDonald" <blog@rivadpm.com> |
|---|---|
| Date | 2015-04-01 15:54 +0100 |
| Message-ID | <mfh0pu$43m$1@dont-email.me> |
| In reply to | #37806 |
on 01/04/2015 15:38:00, Bernd Paysan wrote: > Gerry Jackson wrote: >> Incidentally I'm still using what is now a very old version of GForth, >> 0.7.0, which I believe was the last one for which a Windows executable >> was made available. Not everybody wants to compile from the latest >> source code in your repository - after all I primarily develop and use >> my own system. It would be better for GForth's image if a more recent >> version of GForth was made available as a Windows executable. > > Unfortunately, the Windows users are the ones who need the most care > and give back the least ;-). I could try to build a recent snapshot, > but really, we need a volunteer for that. Somebody who uses Windows > for more than just the annual tax report... > I've tried in the distant past, but unsuccesfully. Let me know what the steps are and I'll install the tools and attempt it again.
[toc] | [prev] | [next] | [standalone]
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Date | 2015-04-01 17:41 +0200 |
| Message-ID | <mfh3i8$ffq$1@dont-email.me> |
| In reply to | #37808 |
Alex McDonald wrote: > I've tried in the distant past, but unsuccesfully. Let me know what the > steps are and I'll install the tools and attempt it again. You need a cygwin installation (or two, Cygwin + Cygwin64), with gcc, git, binutils, autoconf/automake, make, libffi, and with Gforth now supporting libraries like X and OpenGL, you might want an Xserver+Xlib stuff, too. As long as the Forth SWIG module hasn't been merged back into Swig, you need to compile and install either Gerald's or mine SWIG fork on Github: https://github.com/forthy42/swig https://github.com/GeraldWodni/swig whichever is newer ;-). Primary git repository is on Savannah: git clone git://git.savannah.gnu.org/gforth.git If you want to commit changes, we can add you as member. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o ID: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* http://bernd-paysan.de/
[toc] | [prev] | [next] | [standalone]
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Date | 2015-04-01 18:24 +0200 |
| Message-ID | <mfh626$p54$1@dont-email.me> |
| In reply to | #37815 |
Bernd Paysan wrote: > Alex McDonald wrote: >> I've tried in the distant past, but unsuccesfully. Let me know what the >> steps are and I'll install the tools and attempt it again. > > You need a cygwin installation (or two, Cygwin + Cygwin64), with gcc, git, > binutils, autoconf/automake, make, libffi, and with Gforth now supporting > libraries like X and OpenGL, you might want an Xserver+Xlib stuff, too. And Texinfo (i.e. TeXlive) to build the documentation, plus Inno Setup for the setup.exe generation. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o ID: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* http://bernd-paysan.de/
[toc] | [prev] | [next] | [standalone]
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Date | 2015-04-02 05:27 +0200 |
| Message-ID | <mficu3$8el$1@dont-email.me> |
| In reply to | #37817 |
Bernd Paysan wrote: > Bernd Paysan wrote: > >> Alex McDonald wrote: >>> I've tried in the distant past, but unsuccesfully. Let me know what the >>> steps are and I'll install the tools and attempt it again. I finally managed to compile it with the 64 bit Cygwin version (some old mmap bug of Cygwin apparently made it into Cygwin64, and the old fix fortunately works there ;-). If you want to try, an "inofficial" snapshot is now here: http://bernd-paysan.de/gforth-0.7.9_20150221.exe If someone confirms that it works, I'll make it an official snapshot (probably after updating the snapshot date). -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o ID: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* http://bernd-paysan.de/
[toc] | [prev] | [next] | [standalone]
| From | Coos Haak <chforth@hccnet.nl> |
|---|---|
| Date | 2015-04-02 12:38 +0200 |
| Message-ID | <9dx7nwf774mu$.jd50glhc7mu2$.dlg@40tude.net> |
| In reply to | #37827 |
Op Thu, 02 Apr 2015 05:27:52 +0200 schreef Bernd Paysan: > Bernd Paysan wrote: > >> Bernd Paysan wrote: >> >>> Alex McDonald wrote: >>>> I've tried in the distant past, but unsuccesfully. Let me know what the >>>> steps are and I'll install the tools and attempt it again. > > I finally managed to compile it with the 64 bit Cygwin version (some old > mmap bug of Cygwin apparently made it into Cygwin64, and the old fix > fortunately works there ;-). If you want to try, an "inofficial" snapshot > is now here: > > http://bernd-paysan.de/gforth-0.7.9_20150221.exe > > If someone confirms that it works, I'll make it an official snapshot > (probably after updating the snapshot date). I tried, but failed to download. Norton Internet Security deleted it and thinks that WS.Reputation.1 is the origin of the thread. -- Coos CHForth, 16 bit DOS applications http://home.hccnet.nl/j.j.haak/forth.html
[toc] | [prev] | [next] | [standalone]
| From | "Alex McDonald" <blog@rivadpm.com> |
|---|---|
| Date | 2015-04-02 15:45 +0100 |
| Message-ID | <mfjkjp$ce9$1@dont-email.me> |
| In reply to | #37834 |
on 02/04/2015 11:38:06, Coos Haak wrote: > Op Thu, 02 Apr 2015 05:27:52 +0200 schreef Bernd Paysan: > >> Bernd Paysan wrote: >> >>> Bernd Paysan wrote: >>> >>>> Alex McDonald wrote: >>>>> I've tried in the distant past, but unsuccesfully. Let me know what the >>>>> steps are and I'll install the tools and attempt it again. >> >> I finally managed to compile it with the 64 bit Cygwin version (some old >> mmap bug of Cygwin apparently made it into Cygwin64, and the old fix >> fortunately works there ;-). If you want to try, an "inofficial" snapshot >> is now here: >> >> http://bernd-paysan.de/gforth-0.7.9_20150221.exe >> >> If someone confirms that it works, I'll make it an official snapshot >> (probably after updating the snapshot date). > > I tried, but failed to download. Norton Internet Security deleted it > and thinks that WS.Reputation.1 is the origin of the thread. > Worked OK for me (Macafee is my scanner). The intsall had a glitch on a chmod in the shell; it fails and waits for terminal input. An enter causes the rest to isnstall with I think warnings. But they went by so fast I couldn't tell. gforth.exe works fine.
[toc] | [prev] | [next] | [standalone]
| From | "Alex McDonald" <blog@rivadpm.com> |
|---|---|
| Date | 2015-04-02 17:25 +0100 |
| Message-ID | <mfjqfj$5eo$1@dont-email.me> |
| In reply to | #37839 |
on 02/04/2015 15:45:04, "Alex McDonald" wrote:
> on 02/04/2015 11:38:06, Coos Haak wrote:
>> Op Thu, 02 Apr 2015 05:27:52 +0200 schreef Bernd Paysan:
>>
>>> Bernd Paysan wrote:
>>>
>>>> Bernd Paysan wrote:
>>>>
>>>>> Alex McDonald wrote:
>>>>>> I've tried in the distant past, but unsuccesfully. Let me know what the
>>>>>> steps are and I'll install the tools and attempt it again.
>>>
>>> I finally managed to compile it with the 64 bit Cygwin version (some old
>>> mmap bug of Cygwin apparently made it into Cygwin64, and the old fix
>>> fortunately works there ;-). If you want to try, an "inofficial" snapshot
>>> is now here:
>>>
>>> http://bernd-paysan.de/gforth-0.7.9_20150221.exe
>>>
>>> If someone confirms that it works, I'll make it an official snapshot
>>> (probably after updating the snapshot date).
>>
>> I tried, but failed to download. Norton Internet Security deleted it
>> and thinks that WS.Reputation.1 is the origin of the thread.
>>
>
> Worked OK for me (Macafee is my scanner). The intsall had a glitch on
> a chmod in the shell; it fails and waits for terminal input. An enter
> causes the rest to isnstall with I think warnings. But they went by so
> fast I couldn't tell. gforth.exe works fine.
>
bash.exe: warning: could not find /tmp, please create!
bash.exe: warning: could not find /tmp, please create!
data offset=-FE40
code offset=D0
xt offset=B0
label offset=90
45D8 6FFFF7A3A48 6FFFF793A48
45E0 6FFFF7A3A40 6FFFF793A40
4650 6FFFF7600B0 6FFFF7500B0
46C0 6FFFF760120 6FFFF750120
/gforthmi: line 68: chmod: command not found
Wait here, then on enter it runs several commands with warnings that I
can't capture.
[toc] | [prev] | [next] | [standalone]
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Date | 2015-04-03 02:00 +0200 |
| Message-ID | <mfkl66$h0b$1@dont-email.me> |
| In reply to | #37842 |
Alex McDonald wrote: > on 02/04/2015 15:45:04, "Alex McDonald" wrote: >> Worked OK for me (Macafee is my scanner). The intsall had a glitch on >> a chmod in the shell; it fails and waits for terminal input. An enter >> causes the rest to isnstall with I think warnings. But they went by so >> fast I couldn't tell. gforth.exe works fine. >> > > bash.exe: warning: could not find /tmp, please create! > bash.exe: warning: could not find /tmp, please create! > data offset=-FE40 > code offset=D0 > xt offset=B0 > label offset=90 > 45D8 6FFFF7A3A48 6FFFF793A48 > 45E0 6FFFF7A3A40 6FFFF793A40 > 4650 6FFFF7600B0 6FFFF7500B0 > 46C0 6FFFF760120 6FFFF750120 > /gforthmi: line 68: chmod: command not found > > Wait here, then on enter it runs several commands with warnings that I > can't capture. Those warnings are most likely diagnostic outputs. The chmod sets the +x attribute for the image, something you don't have (and therefore don't need) on Windows. To check if the rest of the install did its job, do a .fpath in Gforth. If it's pringing out your install directory, it's fine. I don't use registry or such, I patch the binaries instead. With some antivirus programs, this fails. Question: How many people need a 32 bit Gforth on Windows? Is there any demand for that or is the 64 bit Gforth just fine? AMD64 has been introduced more than 10 years ago, and Windows XP has reached EOL; if you want to be vintage, you can as well use the old Gforth 0.7 executable ;-). -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o ID: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* http://bernd-paysan.de/
[toc] | [prev] | [next] | [standalone]
| From | Gerry Jackson <gerry@jackson9000.fsnet.co.uk> |
|---|---|
| Date | 2015-04-03 20:49 +0100 |
| Message-ID | <mfmqqr$odp$1@dont-email.me> |
| In reply to | #37855 |
On 03/04/2015 01:00, Bernd Paysan wrote: > Question: How many people need a 32 bit Gforth on Windows? Is there any > demand for that or is the 64 bit Gforth just fine? AMD64 has been > introduced more than 10 years ago, and Windows XP has reached EOL; if you > want to be vintage, you can as well use the old Gforth 0.7 executable ;-). I still use 32 bit Windows 7, I've never felt the need to move to 64 bits and probably won't until I get a new computer. -- Gerry
[toc] | [prev] | [next] | [standalone]
| From | "Elizabeth D. Rather" <erather@forth.com> |
|---|---|
| Date | 2015-04-03 11:08 -1000 |
| Message-ID | <AeidnRQFiKOunILInZ2dnUU7-SWdnZ2d@supernews.com> |
| In reply to | #37896 |
On 4/3/15 9:49 AM, Gerry Jackson wrote: > On 03/04/2015 01:00, Bernd Paysan wrote: >> Question: How many people need a 32 bit Gforth on Windows? Is there any >> demand for that or is the 64 bit Gforth just fine? AMD64 has been >> introduced more than 10 years ago, and Windows XP has reached EOL; if you >> want to be vintage, you can as well use the old Gforth 0.7 executable >> ;-). > > I still use 32 bit Windows 7, I've never felt the need to move to 64 > bits and probably won't until I get a new computer. > I use 32-bit Forth on 64-bit Win7 and MacOS. What is the perceived advantage of going 64-bit beyond generally "keeping up with fashion"? Cheers, Elizabeth -- ================================================== Elizabeth D. Rather (US & Canada) 800-55-FORTH FORTH Inc. +1 310.999.6784 5959 West Century Blvd. Suite 700 Los Angeles, CA 90045 http://www.forth.com "Forth-based products and Services for real-time applications since 1973." ==================================================
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2015-04-03 14:14 -0700 |
| Message-ID | <87fv8g7w4l.fsf@jester.gateway.sonic.net> |
| In reply to | #37899 |
"Elizabeth D. Rather" <erather@forth.com> writes: > I use 32-bit Forth on 64-bit Win7 and MacOS. What is the perceived > advantage of going 64-bit beyond generally "keeping up with fashion"? 64-bit programs usually run a lot faster. Wider data transfers, more cpu registers (depending), etc. Plus the much larger address space, which some memory hungry programs actually use.
[toc] | [prev] | [next] | [standalone]
Page 2 of 4 — ← Prev page 1 [2] 3 4 Next page →
Back to top | Article view | comp.lang.forth
csiph-web