--
--
Duke
** Text only please. Bottom post is best for me **

On Sunday, January 9, 2022 at 4:33:52 PM UTC-5, Sidney Reilley wrote:
> --
> --
> Duke
> ** Text only please. Bottom post is best for me **

Ok, here's the bottom post, text only. I hope this helps.

--

Rick C.

- Get 1,000 miles of free Supercharging
- Tesla referral code - https://ts.la/richard11209

On 2022-01-09, Rick C <gnuarm.deletethisbit@gmail.com> wrote:
> On Sunday, January 9, 2022 at 4:33:52 PM UTC-5, Sidney Reilley wrote:
>> --
>> --
>> Duke
>> ** Text only please. Bottom post is best for me **
>
>
> Ok, here's the bottom post, text only. I hope this helps.
>

--
--
Duke
** Text only please. Bottom post is best for me **

On Sun, 9 Jan 2022 21:33:50 -0000 (UTC)
Sidney Reilley <sidney.reilley.ii@gmail.com> wrote:

Got rid of slrn! Now using sylpheed!
Sorry about the BS.

I was saying that I'm revisiting Forth using Pforth and Brodie's
"Starting Forth". I'm of course working through his examples.
Pforth doesn't seem to support the words SPACE and SPACES.
Should I be loading another dictionary to get those words? TIA ..
--
Duke
** Text only please. Bottom post is best for me **

On 10/01/2022 12:56, Sidney Reilley wrote:
> On Sun, 9 Jan 2022 21:33:50 -0000 (UTC)
> Sidney Reilley <sidney.reilley.ii@gmail.com> wrote:
>
> Got rid of slrn! Now using sylpheed!
> Sorry about the BS.
>
> I was saying that I'm revisiting Forth using Pforth and Brodie's
> "Starting Forth". I'm of course working through his examples.
> Pforth doesn't seem to support the words SPACE and SPACES.
> Should I be loading another dictionary to get those words? TIA ..

That would be Phil Burk's pforth?

I've never compiled this system but SPACE and SPACES are included
in the file 'system.fth'. I see mention of

pforth -i system.fth

which claims to rebuild the system so you might try that.

On Mon, 10 Jan 2022 14:27:43 +1100
dxforth <dxforth@gmail.com> wrote:

> On 10/01/2022 12:56, Sidney Reilley wrote:
> > On Sun, 9 Jan 2022 21:33:50 -0000 (UTC)
> > Sidney Reilley <sidney.reilley.ii@gmail.com> wrote:
> >
> > Got rid of slrn! Now using sylpheed!
> > Sorry about the BS.
> >
> > I was saying that I'm revisiting Forth using Pforth and Brodie's
> > "Starting Forth". I'm of course working through his examples.
> > Pforth doesn't seem to support the words SPACE and SPACES.
> > Should I be loading another dictionary to get those words?
> > TIA ..
>
> That would be Phil Burk's pforth?

yes.

> I've never compiled this system but SPACE and SPACES are included
> in the file 'system.fth'. I see mention of
>
> pforth -i system.fth
>
> which claims to rebuild the system so you might try that.

I'll give it a shot! Thx. If all else fails, I've got gforth
installed as well. Probably should stick with it.
--
Duke
** Text only please. Bottom post is best for me **

On Mon, 10 Jan 2022 14:27:43 +1100
dxforth <dxforth@gmail.com> wrote:

> On 10/01/2022 12:56, Sidney Reilley wrote:
> > On Sun, 9 Jan 2022 21:33:50 -0000 (UTC)
> > Sidney Reilley <sidney.reilley.ii@gmail.com> wrote:
> >
> > Got rid of slrn! Now using sylpheed!
> > Sorry about the BS.
> >
> > I was saying that I'm revisiting Forth using Pforth and Brodie's
> > "Starting Forth". I'm of course working through his examples.
> > Pforth doesn't seem to support the words SPACE and SPACES.
> > Should I be loading another dictionary to get those words?
> > TIA ..
>
> That would be Phil Burk's pforth?
>
> I've never compiled this system but SPACE and SPACES are included
> in the file 'system.fth'. I see mention of
>
> pforth -i system.fth
>
> which claims to rebuild the system so you might try that.

No Joy!

[quote]
pforth -i system.fth

PForth V21
Including: system.fth
pfIncludeFile could not open system.fth
{/quote]

Maybe I need to scoop it from his site? I'll give it a shot.
--
Duke
** Text only please. Bottom post is best for me **

On 10/01/2022 16:15, Sidney Reilley wrote:
> On Mon, 10 Jan 2022 14:27:43 +1100
> dxforth <dxforth@gmail.com> wrote:
>
>> On 10/01/2022 12:56, Sidney Reilley wrote:
>> > On Sun, 9 Jan 2022 21:33:50 -0000 (UTC)
>> > Sidney Reilley <sidney.reilley.ii@gmail.com> wrote:
>> >
>> > Got rid of slrn! Now using sylpheed!
>> > Sorry about the BS.
>> >
>> > I was saying that I'm revisiting Forth using Pforth and Brodie's
>> > "Starting Forth". I'm of course working through his examples.
>> > Pforth doesn't seem to support the words SPACE and SPACES.
>> > Should I be loading another dictionary to get those words?
>> > TIA ..
>>
>> That would be Phil Burk's pforth?
>>
>> I've never compiled this system but SPACE and SPACES are included
>> in the file 'system.fth'. I see mention of
>>
>> pforth -i system.fth
>>
>> which claims to rebuild the system so you might try that.
>
> No Joy!
>
> [quote]
> pforth -i system.fth
>
> PForth V21
> Including: system.fth
> pfIncludeFile could not open system.fth
> {/quote]
>
> Maybe I need to scoop it from his site? I'll give it a shot.

I managed to compile a base pforth executable under Windows. system.fth
is located in the 'fth' directory so I moved the exec there and ran:

pforth -i system.fth

which generates pforth.dic. After that pforth boots with SPACE SPACES etc.
loaded.

On Mon, 10 Jan 2022 18:46:47 +1100
dxforth <dxforth@gmail.com> wrote:

[snip]

> > No Joy!
> >
> > [quote]
> > pforth -i system.fth
> >
> > PForth V21
> > Including: system.fth
> > pfIncludeFile could not open system.fth
> > {/quote]
> >
> > Maybe I need to scoop it from his site? I'll give it a shot.
>
> I managed to compile a base pforth executable under Windows.
> system.fth is located in the 'fth' directory so I moved the exec
> there and ran:

I'm on a Linux box! All I have (or can find) is "pforth.dic". How
do you go about compiling "a base pforth"? You new from source?
--
Duke
** Text only please. Bottom post is best for me **

On 11/01/2022 01:26, Sidney Reilley wrote:
> On Mon, 10 Jan 2022 18:46:47 +1100
> dxforth <dxforth@gmail.com> wrote:
>
> [snip]
>
>> > No Joy!
>> >
>> > [quote]
>> > pforth -i system.fth
>> >
>> > PForth V21
>> > Including: system.fth
>> > pfIncludeFile could not open system.fth
>> > {/quote]
>> >
>> > Maybe I need to scoop it from his site? I'll give it a shot.
>>
>> I managed to compile a base pforth executable under Windows.
>> system.fth is located in the 'fth' directory so I moved the exec
>> there and ran:
>
> I'm on a Linux box! All I have (or can find) is "pforth.dic". How
> do you go about compiling "a base pforth"? You new from source?

I used the TCC Win compiler and the pforth sources here:

https://github.com/philburk/pforth

Never used Linux. Perhaps someone here can suggest how to compile
for your platform.

On 01/10/2022 08:26 AM, Sidney Reilley wrote:
> On Mon, 10 Jan 2022 18:46:47 +1100
> dxforth <dxforth@gmail.com> wrote:
>
> [snip]
>
>>> No Joy!
>>>
>>> [quote]
>>> pforth -i system.fth
>>>
>>> PForth V21
>>> Including: system.fth
>>> pfIncludeFile could not open system.fth
>>> {/quote]
>>>
>>> Maybe I need to scoop it from his site? I'll give it a shot.
>>
>> I managed to compile a base pforth executable under Windows.
>> system.fth is located in the 'fth' directory so I moved the exec
>> there and ran:
>
> I'm on a Linux box! All I have (or can find) is "pforth.dic". How
> do you go about compiling "a base pforth"? You new from source?
>

Which Linux?
pforth is available in current Debian repository.

On Tue, 11 Jan 2022 01:54:46 +1100
dxforth <dxforth@gmail.com> wrote:

> I used the TCC Win compiler and the pforth sources here:
>
> https://github.com/philburk/pforth
>
> Never used Linux. Perhaps someone here can suggest how to compile
> for your platform.

You may need to install build tools for your flavour of linux - ask.

view pforth manual at:
http://www.softsynth.com/pforth/pf_ref.php#Compiling-pForth-System

follow link to look at build instructions here:
How to Compile pForth on Unix or Mac
https://github.com/philburk/pforth/wiki/Compiling-on-Unix

then:
mkdir .../github.com/philburke # make place for sources

git clone https://github.com/philburk/pforth.git # pull in source
cd pforth/ # select project folder
ls # take a quick look

cd platforms/unix/ # select unix build folder

make all # run build

ls # take a peek

../pforth # run executable

.." >>" 20 spaces ." \ << " >> << ok

Jan Coombs
--

On Mon, 10 Jan 2022 15:19:47 +0000
Jan Coombs <jenfhaomndgfwutc@murmic.plus.com> wrote:

> then:
> mkdir .../github.com/philburke # make place for sources

cd .../github.com/philburke # select folder for project
> git clone https://github.com/philburk/pforth.git # pull in source

Sorry, pre-post check failed, Jan Coombs

On Mon, 10 Jan 2022 08:59:21 -0600
Richard Owlett <rowlett@cloud85.net> wrote:

> On 01/10/2022 08:26 AM, Sidney Reilley wrote:
> > On Mon, 10 Jan 2022 18:46:47 +1100
> > dxforth <dxforth@gmail.com> wrote:
> >
> > [snip]
> >
> >>> No Joy!
> >>>
> >>> [quote]
> >>> pforth -i system.fth
> >>>
> >>> PForth V21
> >>> Including: system.fth
> >>> pfIncludeFile could not open system.fth
> >>> {/quote]
> >>>
> >>> Maybe I need to scoop it from his site? I'll give it a shot.
> >>
> >> I managed to compile a base pforth executable under Windows.
> >> system.fth is located in the 'fth' directory so I moved the
> >> exec there and ran:
> >
> > I'm on a Linux box! All I have (or can find) is "pforth.dic".
> > How do you go about compiling "a base pforth"? You new from
> > source?
> >
>
> Which Linux?
> pforth is available in current Debian repository.

I know! That's what I'm running on my antiX Linux box.
--
Duke
** Text only please. Bottom post is best for me **

On Mon, 10 Jan 2022 15:19:47 +0000
Jan Coombs <jenfhaomndgfwutc@murmic.plus.com> wrote:

> On Tue, 11 Jan 2022 01:54:46 +1100
> dxforth <dxforth@gmail.com> wrote:
>
> > I used the TCC Win compiler and the pforth sources here:
> >
> > https://github.com/philburk/pforth
> >
> > Never used Linux. Perhaps someone here can suggest how to
> > compile for your platform.
>
> You may need to install build tools for your flavour of linux -
> ask.
>
> view pforth manual at:
> http://www.softsynth.com/pforth/pf_ref.php#Compiling-pForth-System
>
> follow link to look at build instructions here:
> How to Compile pForth on Unix or Mac
> https://github.com/philburk/pforth/wiki/Compiling-on-Unix
>
> then:
> mkdir .../github.com/philburke # make place for sources
>
> git clone https://github.com/philburk/pforth.git # pull in
> source cd pforth/ # select project folder
> ls # take a quick look
>
> cd platforms/unix/ # select unix build folder
>
> make all # run build
>
> ls # take a peek
>
> ./pforth # run executable
>
> ." >>" 20 spaces ." \ << " >> << ok

Thanks for the instructions! I use github all the time. I wasn't
too sure what dxforth meant by "recompiling"? Now I know that he
meant re-build the source code and not Forth re-building itself or
some such. Thanks again.

--
Duke
** Text only please. Bottom post is best for me **

On Mon, 10 Jan 2022 15:24:53 +0000
Jan Coombs <jenfhaomndgfwutc@murmic.plus.com> wrote:

> On Mon, 10 Jan 2022 15:19:47 +0000
> Jan Coombs <jenfhaomndgfwutc@murmic.plus.com> wrote:
>
> > then:
> > mkdir .../github.com/philburke # make place for sources
>
> cd .../github.com/philburke # select folder for project
>
> > git clone https://github.com/philburk/pforth.git # pull in
> > source
>
>
> Sorry, pre-post check failed, Jan Coombs
>

Got it done! Thx again - works like a charm now!
--
Duke
** Text only please. Bottom post is best for me **

On Mon, 10 Jan 2022 15:24:53 +0000
Jan Coombs <jenfhaomndgfwutc@murmic.plus.com> wrote:

[snip]

The only way I got it to work is by telling it where the default
dictionary was. In your instructions, you simply executed `pforth'.

pforth -d ~/bin/pforth.dic

However, it works well so far.
--
Duke
** Text only please. Bottom post is best for me **

Sidney Reilley <sidney.reilley.ii@gmail.com> writes:
> I'm on a Linux box! All I have (or can find) is "pforth.dic". How
> do you go about compiling "a base pforth"? You new from source?

Why don't you use gforth instead of pforth? Gforth is very full
featured and there is probably an installable package for your Linux
distro. E.g. if you are using Debian, say "apt-get install gforth".

On 11/01/2022 05:05, Sidney Reilley wrote:
> On Mon, 10 Jan 2022 15:24:53 +0000
> Jan Coombs <jenfhaomndgfwutc@murmic.plus.com> wrote:
>
>> On Mon, 10 Jan 2022 15:19:47 +0000
>> Jan Coombs <jenfhaomndgfwutc@murmic.plus.com> wrote:
>>
>> > then:
>> > mkdir .../github.com/philburke # make place for sources
>>
>> cd .../github.com/philburke # select folder for project
>>
>> > git clone https://github.com/philburk/pforth.git # pull in
>> > source
>>
>>
>> Sorry, pre-post check failed, Jan Coombs
>>
>
> Got it done! Thx again - works like a charm now!

Great. OTOH I was unable to build the f/p version

#define PF_SUPPORT_FP

The compiler spewed out errors. Knowing little-to-nothing about C
I didn't pursue it further.

On Monday, January 10, 2022 at 6:50:29 PM UTC-6, dxforth wrote:
> On 11/01/2022 05:05, Sidney Reilley wrote:
> > On Mon, 10 Jan 2022 15:24:53 +0000
> > Jan Coombs <jenfhaom...@murmic.plus.com> wrote:
> >
> >> On Mon, 10 Jan 2022 15:19:47 +0000
> >> Jan Coombs <jenfhaom...@murmic.plus.com> wrote:
> >>
> >> > then:
> >> > mkdir .../github.com/philburke # make place for sources
> >>
> >> cd .../github.com/philburke # select folder for project
> >>
> >> > git clone https://github.com/philburk/pforth.git # pull in
> >> > source
> >>
> >>
> >> Sorry, pre-post check failed, Jan Coombs
> >>
> >
> > Got it done! Thx again - works like a charm now!
> Great. OTOH I was unable to build the f/p version
>
> #define PF_SUPPORT_FP
>
> The compiler spewed out errors. Knowing little-to-nothing about C
> I didn't pursue it further.

My version has space defined and its:
: space bl emit ;

and you can define spaces as:

: spaces 0 do space loop ;

This is just a basic definition. You could add checks for an empty stack.

On 11/01/2022 15:21, tom d wrote:
> On Monday, January 10, 2022 at 6:50:29 PM UTC-6, dxforth wrote:
>> On 11/01/2022 05:05, Sidney Reilley wrote:
>> > On Mon, 10 Jan 2022 15:24:53 +0000
>> > Jan Coombs <jenfhaom...@murmic.plus.com> wrote:
>> >
>> >> On Mon, 10 Jan 2022 15:19:47 +0000
>> >> Jan Coombs <jenfhaom...@murmic.plus.com> wrote:
>> >>
>> >> > then:
>> >> > mkdir .../github.com/philburke # make place for sources
>> >>
>> >> cd .../github.com/philburke # select folder for project
>> >>
>> >> > git clone https://github.com/philburk/pforth.git # pull in
>> >> > source
>> >>
>> >>
>> >> Sorry, pre-post check failed, Jan Coombs
>> >>
>> >
>> > Got it done! Thx again - works like a charm now!
>> Great. OTOH I was unable to build the f/p version
>>
>> #define PF_SUPPORT_FP
>>
>> The compiler spewed out errors. Knowing little-to-nothing about C
>> I didn't pursue it further.
>
>
> My version has space defined and its:
> : space bl emit ;
>
> and you can define spaces as:
>
> : spaces 0 do space loop ;
>
> This is just a basic definition. You could add checks for an empty stack.

Strictly speaking that should be:

: spaces ( +n -- ) 0 max 0 ?do space loop ;

The inbuilt '0 MAX' is a historical artefact. Programmers computing
padding spaces didn't have to worry about 'negative' values.

On Tue, 11 Jan 2022 11:50:23 +1100
dxforth <dxforth@gmail.com> wrote:

[snip]
> Great. OTOH I was unable to build the f/p version

The default unix build here seems to include f/p (Debian, Intel, 64b):
1234.5678e1 f. 12345.68 ok

> #define PF_SUPPORT_FP

The unix makefile here contains:
XCPPFLAGS = -DPF_SUPPORT_FP -D_DEFAULT_SOURCE -D_GNU_SOURCE
and other instances of "fp".
Where is the
#define PF_SUPPORT_FP
in yours?

Jan Coombs
--

On 12/01/2022 00:27, Jan Coombs wrote:
> On Tue, 11 Jan 2022 11:50:23 +1100
> dxforth <dxforth@gmail.com> wrote:
>
> [snip]
>> Great. OTOH I was unable to build the f/p version
>
> The default unix build here seems to include f/p (Debian, Intel, 64b):
> 1234.5678e1 f. 12345.68 ok
>
>> #define PF_SUPPORT_FP
>
> The unix makefile here contains:
> XCPPFLAGS = -DPF_SUPPORT_FP -D_DEFAULT_SOURCE -D_GNU_SOURCE
> and other instances of "fp".
> Where is the
> #define PF_SUPPORT_FP
> in yours?

There was no makefile for Win other than a project file for VisualStudio.
Not knowing how to make one, I just created a file of includes. That
worked until I declared PF_SUPPORT_FP ...

#define PF_SUPPORT_FP

#include "pforth\csrc\pf_all.h"
#include "pforth\csrc\pf_cglue.h"
#include "pforth\csrc\pf_clib.h"
#include "pforth\csrc\pf_core.h"
#include "pforth\csrc\pf_float.h"
#include "pforth\csrc\pf_guts.h"
#include "pforth\csrc\pf_host.h"
#include "pforth\csrc\pf_inc1.h"
#include "pforth\csrc\pf_io.h"
#include "pforth\csrc\pf_mem.h"
#include "pforth\csrc\pf_save.h"
#include "pforth\csrc\pf_text.h"
#include "pforth\csrc\pf_types.h"
#include "pforth\csrc\pf_win32.h"
#include "pforth\csrc\pf_words.h"
#include "pforth\csrc\pfcompfp.h"
#include "pforth\csrc\pfcompil.h"
#include "pforth\csrc\pfdicdat_arm.h"
#include "pforth\csrc\pfinnrfp.h"
#include "pforth\csrc\pforth.h"

#include "pforth\csrc\pfcompil.c"
#include "pforth\csrc\pfcustom.c"
#include "pforth\csrc\pf_cglue.c"
#include "pforth\csrc\pf_clib.c"
#include "pforth\csrc\pf_core.c"
#include "pforth\csrc\pf_inner.c"
#include "pforth\csrc\pf_io.c"
#include "pforth\csrc\pf_io_none.c"
#include "pforth\csrc\pf_main.c"
#include "pforth\csrc\pf_mem.c"
#include "pforth\csrc\pf_save.c"
#include "pforth\csrc\pf_text.c"
#include "pforth\csrc\pf_words.c"
#include "pforth\csrc\stdio\pf_fileio_stdio.c"
#include "pforth\csrc\win32_console\pf_io_win32_console.c"

> The only way I got it to work is by telling it where the default
> dictionary was. In your instructions, you simply executed `pforth'.
>
> pforth -d ~/bin/pforth.dic

Here on Slackware64 it works with no problems whatsoever. Of course SPACE / SPACES do exist in its dictionary:

#v+
PForth V27-LE/64, built Feb 19 2018 01:56:44
pForth loading dictionary from file /usr/share/pforth/v28/pforth.dic
File format version is 9
Name space size = 120000
Code space size = 300000
Entry Point = 0
Cell Size = 8
Little Endian Dictionary

space ok
Stack<10>
4 spaces ok
Stack<10>
12 spaces ok
Stack<10>
#v-

Multiple spaces in my reply have been "compressed" by news server. They are correctly displayed "locally" ofc.