Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| How should size of program grow with size of problem? jvn@fermi.clas.virginia.edu (Julian V. Noble) (1993-10-28) |
| Re: How should size of program grow with size of problem? henry@zoo.toronto.edu (1993-11-03) |
| reusing ADT, not implementation (was Re: How should size ... ?) jejones@microware.com (1993-11-04) |
| Re: reusing ADT, not implementation (was Re: How should size ... ?) preston@dawn.cs.rice.edu (1993-11-05) |
| Newsgroups: | comp.compilers |
| From: | jejones@microware.com (James Jones) |
| Keywords: | OOP, design |
| Organization: | Microware Systems Corp., Des Moines, Iowa |
| References: | 93-10-136 93-11-032 |
| Date: | Thu, 4 Nov 1993 17:28:23 GMT |
henry@zoo.toronto.edu (Henry Spencer) writes:
>Indeed, there are a significant number of people who think that once you
>strip away the OOH (Object-Oriented Hype), being able to reuse
>*interfaces* is much more important than being able to reuse code.
Sounds like what Schwartz et al. (Dewar, perhaps?) did with SETL, which
would let you fine tune the implementation of particular instances of its
basic notions (set, relation, etc.) once you had the code working. The
canonical references are in POPL and CACM, I believe, but they've faded
from my memory.
James Jones
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.