home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.object
- Path: sparky!uunet!stanford.edu!ames!think.com!rpi!night
- From: night@acm.rpi.edu (Trip Martin)
- Subject: Re: objects and closures
- Message-ID: <w9l1smp@rpi.edu>
- Nntp-Posting-Host: hermes.acm.rpi.edu
- Reply-To: night@acm.rpi.edu
- References: <1992Oct27.205320.13271@twg.com> <9210302223.AA11001@cs.columbia.edu> <720756315@sheol.UUCP> <Bx5DFt.7z3@dcs.ed.ac.uk> <BEVAN.92Nov3182229@hippo.cs.man.ac.uk> <720937337@sheol.UUCP> <Bx8zy5.4n5@dcs.ed.ac.uk> <BEVAN.92Nov7123646@hippo.cs.man.ac.uk>
- Distribution: na
- Date: Sun, 8 Nov 1992 16:41:30 GMT
- Lines: 14
-
- In <BEVAN.92Nov7123646@hippo.cs.man.ac.uk> bevan@cs.man.ac.uk (Stephen J Bevan) writes:
-
- >I realise that this is comp.object, however I would hope that most
- >readers are not so partisan as think reuse implies OOP. There are
- >many ways to reuse code, inheriting from it is only _one_ method and I
- >would venture not even the dominant one, even in OOL programs.
-
- What other methods of reuse are there?
- --
- Trip Martin
- night@acm.rpi.edu
- --
- Trip Martin
- night@acm.rpi.edu
-