Re: Use of ';' in Forth Compiler
- From: Albert van der Horst <albert@xxxxxxxxxxxxxxxxxx>
- Date: 29 Jun 2005 23:54:11 GMT
In article <2005Jun29.145508@xxxxxxxxxxxxxxxxxxxxxxxxxx>,
Anton Ertl <anton@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>Albert van der Horst <albert@xxxxxxxxxxxxxxxxxx> writes:
>>I see two main reasons.
>>1. the stuff is not actually used
>>2. the stuff is not mutally used by the FSL contributors themselves,
>>such that A. each contribution is a world on its on.
>> B. they have to include the kitchen sink, in case you
>> don't have one.
>
>Or worse, they don't include it, but ask you to include it yourself.
I try to convey that somehow the critical mass of users is not
reached. Don't you agree with that?
>
>>I may draw attention to reason 1.
>>
>>Suppose I want a file to block utility.
>>The canonical way how that looks in c is:
>>convert <x.src >x.blk
>>(Under Unices, redirection under windows isn't really usable.)
>
>Then it's not a canonical way, is it?
For Unix it is.
>>If I come up with convert.c you can build the program:
>> make convert
>
>For many source packages this will give you something like
>
>make: *** No rule to make target `convert'. Stop.
On a typical Unix make uses its build in rules
to do
$(CC) $(CFLAGS) convert.c -o convert
or some such.
It may fail, but I would expect some other message then.
(I hate that the gnu make configuration is burned in, such that no
Forth rules can be added.)
>
>However, what successful source packages have is a README file that
>explains how to install it, or they point to the INSTALL file in
>README, and INSTALL explains how to install it. The FSL components
>don't have this.
>
>>That is not how Forth programs work in general.
>>[lina tries to do something about this.
>> lina -c convert.frt ;convert<x.src>x.blk
>>This is not influential.]
>
>It's horrible; what's wrong with
>
>lina convert.frt <x.src >x.blk
The usual things.
1.
The user must be aware how to run a Forth program. This is too much to
ask. The bottom line is that Forth programs will not be used. We live
in a cruel world.
2.
If convert.frt is a considerable program, its on the fly compilation
takes considerable time. That is what compilation (versus
interpretation) is about.
I would not recommend ciasdis otherwise. It takes several minutes
to load the generic assembler, the 80386 instruction, the Pentium
instructions, the two pass additions, the segment and label classes
and the code crawler.
>Something like that would work with Gforth (although writing programs
>to read from standard input has some issues). You can even rename
>convert.frt to convert, and prepend a line like
>
>#! /usr/local/bin/gforth
>
>and you can use the same command line as used above for C:
>
>convert <x.src >x.blk
That is a practice I find a good idea. Also it is good if Forth
implementers make it easy to handle standard input, or at least
document it sufficiently to make it possible.
By the way I would not rename the file, as it consists of Forth code:
convert.frt <x.src >x.blk
This suggest that you can look in the file, and maybe edit it,
which is correct. It is also in line with the way other scripting
languages are using extensions.
E.g. you can inspect an executable perl script :
more /usr/bin/ripit.pl
>- anton
Groetjes Albert
--
--
Albert van der Horst,Oranjestr 8,3511 RA UTRECHT,THE NETHERLANDS
Economic growth -- like all pyramid schemes -- ultimately falters.
albert@xxxxxxxxxxxxxxxxxx http://home.hccnet.nl/a.w.m.van.der.horst
.
- References:
- Re: Use of ';' in Forth Compiler
- From: Julian V. Noble
- Re: Use of ';' in Forth Compiler
- From: Albert van der Horst
- Re: Use of ';' in Forth Compiler
- From: Anton Ertl
- Re: Use of ';' in Forth Compiler
- Prev by Date: Re: Book - Programming Forth
- Next by Date: Re: Patching
- Previous by thread: Re: Use of ';' in Forth Compiler
- Next by thread: Re: Use of ';' in Forth Compiler
- Index(es):
Relevant Pages
|
|
