home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!van-bc!rsoft!mindlink!a684
- From: Nick_Janow@mindlink.bc.ca (Nick Janow)
- Newsgroups: comp.lang.forth
- Subject: Personal vs Standard
- Message-ID: <14926@mindlink.bc.ca>
- Date: 7 Sep 92 22:01:12 GMT
- Organization: MIND LINK! - British Columbia, Canada
- Distribution: world
- Lines: 34
-
- Here's an interesting message that shows a different perspective on the "future
- of Forth" debate:
-
- > From: amos shapir
- > Address : amos@huji.ac.il
- > Group : Usenet.comp.arch
- > Subject : Re: Scientists as Programmers (was Re: Small Language Wanted
- > Posted: 6 Sep 92 13:37:15 GMT
- >
- > hrubin@pop.stat.purdue.edu (Herman Rubin) writes:
- >
- >+ The present compilers translate such things as +, *, &, etc., into some
- >+ version of assembler. Why not allow the user to say how other operations
- >+ will be similarly translated, and add them to the list? These operations
- >+ often produce temporaries; why not tell the user how this is done, and let
- >+ them be added to the list? These would not really complicate the language
- >+ design or the compiler, except insofar as precedence is affected.
- >+
- >+ You want C++, then; or the GNU compilers, which do allow you to dive into
- >+ the compiler's source and create whatever language extensions you wish to.
- >+ The problem is, you'll have no time left in which to do the job originally
- >+ intended...
- >+
- >+ The point is, we can use very simple and flexible meta-tools like assembler
- >+ or FORTH to create our own tools - and end up each using a personal
- >+ hand-tailored language, unique and non portable; or use a standard tool
- >+ which does implement some constructs efficiently and portably, but never all
- >+ we'd ever need.
- >
- > Something to think about... :)
- >
- --
-
- Nick_Janow@mindlink.bc.ca
-