home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!sun-barr!male.EBay.Sun.COM!west.West.Sun.COM!cronkite.Central.Sun.COM!texsun!exucom.exu.ericsson.se!news
- From: exuhag@exu.ericsson.se (James Hague)
- Newsgroups: comp.lang.forth
- Subject: Re: Free Forth
- Message-ID: <1992Aug14.132732.10393@exu.ericsson.se>
- Date: 14 Aug 92 13:27:32 GMT
- References: <1992Aug14.025506.659@csi.uottawa.ca>
- Sender: news@exu.ericsson.se
- Reply-To: exuhag@exu.ericsson.se
- Organization: Ericsson Network Systems, Richardson, TX
- Lines: 26
- Nntp-Posting-Host: s09a05.exu.ericsson.se
-
- Christopher Browne writes:
- >
- >Once in a while, there's a neat article in Communications of the ACM.
- >This month, there's one that rags on "Object Oriented Programming." It
- >criticizes what IS one of the weaknesses; specifically, classes and
- >inheritance.
-
- I've always agreed with more modular languages which let you break
- up your namespace into managable pieces (Modula-2, extended Pascal),
- and I think this is one of my real complaints about Forth. Going the
- full "OOP" route, though, can replace this problem with one of
- inheritance tree managament. As Christopher Browne mentioned, you
- are forced into classifying everything in often unnatural ways. And
- having to rework an inheritance tree in mid-project can be a diaster.
-
- To play devil's advocate, though, the simple view of Forth actually
- works quite well in most cases, and separate vocabularies help things
- a bit. In any OOP or modular language you still have to remember
- functions names and such. You can make Forth seem more organized by
- using standard naming conventions or by manually grouping names together
- by printing up a "namespace map" on paper if you really want some
- asthetics.
-
- --
- James Hague
- exuhag@exu.ericsson.se
-