gforth
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gforth] Gforth Digest, Vol 45, Issue 3: reply to John Chludzinski -


From: James Gere
Subject: Re: [gforth] Gforth Digest, Vol 45, Issue 3: reply to John Chludzinski --loading .fs files
Date: Tue, 22 Dec 2015 17:46:15 -0500


> Today's Topics:
>
>    1. Socket code (John Chludzinski)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 21 Dec 2015 12:24:19 -0500
> From: John Chludzinski <address@hidden>
> To: Gforth <address@hidden>
> Subject: [gforth] Socket code
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
> As a gforth newbie I went online and downloaded sock.fs and tcpserver.fs
> from GitHub. Tried putting the shabang: #! /usr/bin/gforth in the file
> and ruuning it. I have an x86-64 box running Fedora 23.

I think your problem starts here, but I'm not sure which file(s) you edited.  Undo your edits, then try starting gforth from the command line and:
     include sock.fs             \   < --edit for file path
     include  tcpserver.fs   \              ditto.
If this works you'll get "ok" s.  I think Gforth is trying to interpret the file it was just loaded from (including the shebang).

Then look to the manual, info, "gforth --help",etc. to find the startup options you want.  Probably, "gforth -e " or "gforth -i" .  Then you can write your script file.
> *************************************


reply via email to

[Prev in Thread] Current Thread [Next in Thread]