home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.forth
- Path: sparky!uunet!charon.amdahl.com!amdahl!rtech!decwrl!csus.edu!netcom.com!kasajian
- From: kasajian@netcom.com (Kenneth Kasajian)
- Subject: Re: Forth's Adaptability
- Message-ID: <1993Jan26.180836.3711@netcom.com>
- Organization: Netcom - Online Communication Services (408 241-9760 guest)
- References: <1993Jan18.163733.19857@crd.ge.com> <1993Jan19.141925.19029@exu.ericsson.se><1993Jan20.150614.20069@crd.ge.com> <1jk69lINNhjo@news.cerf.net> <BEVAN.93Jan22131846@panda.cs.man.ac.uk>
- Date: Tue, 26 Jan 1993 18:08:36 GMT
- Lines: 26
-
- > [ LMI FORTH has files & blocks, floating point ... etc. ]
-
- > they've [LMI users] had access to these capabilities, if they
- > needed them, for many years.
-
- >And I'm sure they are happy with them, but consider what happens if
- >they decide, for one reason or another, that they don't want to use
- >LMI FORTH anymore, but prefer to use a different vendor's system.
- >What are they to do with all the code they've developed using LMI
- >specific extensions? Unless the "extensions" are either standard or
- >defacto standards then there may be significant effort involved in
- >changing the code, so much so you may have to stick with the system
- >you have even though you know you can get better/cheaper elsewhere
- >(I've suffered just this situation with large amounts of code written
- >using VAX FORTRAN + extensions). This is good for vendors since it
- >keeps users locked into their system, but it is definitely not a good
- >deal for users.
-
- I don't think it is a fair to compare Fortran and Forth in the context
- of portability. If the Vax Fortran + source code had many Forth extensions
- which were not supported by another vendor's Fortran, then you need to
- change your source code considerably. With Forth, it's very easy to
- add the extensions to the language so that the source most often need
- not be changed.
-
- Kenneth Kasajian
-