[comp.lang.forth] Preprocessor for Forth...and why not!

olorin@juniper.uucp (David Weinstein) (08/31/88)

Here are the reasons why I don't want to use a pre-processor to write Forth
code:

1) Debugging...debugging code generated by preprocessors is sheer hell!

2) Efficiency...code generated by a preprocessor will not be as efficient
as the code I write myself.

3) Readability...I really don't want to even have to look at the code being
generated by the preprocessor.

4) Code level. The use of the features you mentioned (strong typing, parameter
lists, etc) remove my primary reasons for using Forth, the ability to write
code at all levels from truly low to truly high. Since I do almost all of my
work under Unix, if I have to put up with parameter lists and "almost"
languages, I might as well use C.

5) I hate parameter lists.

6) Well written Forth, I mean the high level stuff...should look like pseudo
code...I can't do that with the preprocessor getting in my way. Sorry Fraser,
but the top level *should* hide the parameter passing. The top level should
make the algorythm perfectly clear, at lower levels I can look for the pure
and simple mechanics of parameter passing.




-- 
Dave Weinstein
Internet: olorin@walt.cc.utexas.edu
UUCP: {ames,utah-cs,uunet}!ut-sally!ut-emx!{walt.cc.utexas.edu,juniper}!olorin
GEnie: DHWEINSTEIN