Re: [gforth] Windows installer feature request

> > Advanced Installer might be a good tool, but as we are an official GNU > project, we are going to use free software as tools when available. Free > as > in Free Open Source, not as in "no cost". > Perfectly understandable. And Inno Setup is actually a quite good tool, though it doesn't creat

Re: [gforth] shebang support

En/Je/On 2012-10-06 09:44, Andrew Pennebaker escribió / skribis / wrote : >#!/usr/bin/env gforth Use the '#!' word: #! /usr/bin/env gforth Marcos -- http://programandala.net

Re: [gforth] Windows installer feature request

Am Samstag, 6. Oktober 2012, 16:53:13 schrieb Andrew Pennebaker: > The Windows gforth installer > executableworks fine, > except for the fact that it requires the user to manually add > the gforth binaries to the PATH environment variable. Could futur

Re: [gforth] How do I access the program name / argv[0] in Forth?

Am Samstag, 6. Oktober 2012, 14:23:53 schrieb Andrew Pennebaker: > > Am Samstag, 6. Oktober 2012, 13:43:23 schrieb Andrew Pennebaker: > > > > `0 arg` or `argv @ @ cstring>string` both give "gforth" on my > > > > system... > > > > > > Ah, that's better! > > > > > > How could I reliably access the

Re: [gforth] How do I access the program name / argv[0] in Forth?

> Am Samstag, 6. Oktober 2012, 13:43:23 schrieb Andrew Pennebaker: > > > `0 arg` or `argv @ @ cstring>string` both give "gforth" on my system... > > > > Ah, that's better! > > > > How could I reliably access the program name if the user decides to pass > > some options to gforth before supplying th

Re: [gforth] How do I access the program name / argv[0] in Forth?

Am Samstag, 6. Oktober 2012, 13:43:23 schrieb Andrew Pennebaker: > > `0 arg` or `argv @ @ cstring>string` both give "gforth" on my system... > > Ah, that's better! > > How could I reliably access the program name if the user decides to pass > some options to gforth before supplying the source cod

Re: [gforth] How do I access the program name / argv[0] in Forth?

On 2012-10-06 09:55AM, Andrew Pennebaker wrote: >The gforth docs say to access arguments by calling next-arg, but this omits >the program name, which would be printed in a C-like language. > >Since argv[0] seems to be automatically removed from the argument vector in >Forth, is there a special func

Re: [gforth] shebang support

On 2012-10-06 09:44AM, Andrew Pennebaker wrote: >Can we treat shebangs like comments, so that gforth programs can be run >using dot slash notation in Unix? > >hello.fs: > >#!/usr/bin/env gforth We already do; you just need a space after the shebang: #! /usr/bin/env gforth --Josh