home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.forth
- Path: sparky!uunet!van-bc!rsoft!mindlink!a3287
- From: John_Somerville@mindlink.bc.ca (John Somerville)
- Subject: Re: Forth Standard Debate
- Organization: MIND LINK! - British Columbia, Canada
- Date: Tue, 5 Jan 1993 04:13:18 GMT
- Message-ID: <19241@mindlink.bc.ca>
- Sender: news@deep.rsoft.bc.ca (Usenet)
- Lines: 24
-
- I don't see what the problem is. The ANSI standard should only address what
- certain words do, not how they are done. I deal with mechanical and
- electrical standards and it is a distinct advantage not to say how things are
- done, but what needs to be done. If one company writes tighter, faster code
- than another, and they provide source so you can play with the internals...
- great, if they don't then I guess you shouldn't buy it. Really if one is
- going to roll their own, and one wants all the nitty-gritty stuff, what is
- the relevance of the standard? Perhaps the standard implies, that FORTH must
- be regraded as a high level language, with nifty access to assembler. I
- believe that there are good commercial FORTHs available now that allow one to
- do whatever they want, that is there is enough information on intermediate
- words that the interpreter can be tinkered with adequately.
-
- The real advantage of a standard is that one uses it only when it is
- required. Companies may look for programmers who are familiar with ANSI.
- Programmers can communicate with other programmers much better under the
- standard than they do now. And communication is the name of the game.
- Otherwise: dkfd0 j jdkfirn knkduir nfkdirkn mdrjeorn aknrtoeh. I don't think
- you can argue with that.
-
- regards john
- --
- john somerville B.C. Hydro
- affiliations FIG Forth Interest Group
-