home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sw.components
- Path: sparky!uunet!decwrl!sdd.hp.com!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!yale!gumby!destroyer!wsu-cs!vela!cs.uiuc.edu!johnson
- From: johnson@cs.uiuc.edu (Ralph Johnson)
- Subject: Re: Reuse Discussion Topics (Was: Reuse and Software Components)
- Message-ID: <BxAqCL.4qM@cs.uiuc.edu>
- Organization: University of Illinois, Dept. of Comp. Sci., Urbana, IL
- References: <1992Oct29.182814.17630@den.mmc.com> <6597@dove.nist.gov> <1992Nov3.050919.8442@latcs1.lat.oz.au> <Bx56G1.8pr@cs.uiuc.edu> <1992Nov4.230422.19681@latcs1.lat.oz.au>
- Date: Fri, 6 Nov 1992 13:19:32 GMT
- Lines: 17
-
-
- The problem is not just due to the implementation language. Just because
- our systems are iplemented in C does not mean they will work together.
- After all, it seems that 90% of languages today are ultimately implemented
- in C! There was a nice paper at OOPSLA '90 called "When Objects Collide"
- that described problems with combining CLOS libraries. It is necessary
- for interfaces to be the same, and this has only a little to do with what
- the underlying languages are.
-
- The OMG effort is providing a set of standard interfaces that programs
- can use to talk to each other. It explictly permits programs to be written
- in any language. Writing everything in one language helps make for
- common interfaces when the code is all running in the same address space,
- but I'm not sure it helps that much when you are talking about distributed
- applictions.
-
- Ralph Johnson -- University of Illinois at Urbana-Champaign
-