Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!dali.cs.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!pt.cs.cmu.edu!andrew.cmu.edu!aw1r+ From: aw1r+@andrew.cmu.edu (Alfred Benjamin Woodard) Newsgroups: comp.lang.c++ Subject: Re: C++ Linkage, Interface Issues Message-ID: Date: 8 Aug 90 20:19:42 GMT References: <7921@tekgvs.LABS.TEK.COM> <380@taumet.com> < <1990Aug4.233013.20500@cs.columbia.edu> > <383@taumet.com> <9714@rice-chex.ai.mit.edu>, <1070@applix.com> Organization: Carnegie Mellon, Pittsburgh, PA Lines: 23 In-Reply-To: <1070@applix.com> scotte@applix.com (Scott Evernden) writes: > In article (Alfred Benjamin Woodard) writes: I didn't really right this I asked a question and this was the answer? > >What we need is to get away from the current model of separate source > >text files, separate object files, separate compilation, separate linking. > >We need a more integrated environment. For example, typical real-world > >C programs may include thousands of lines of header files for each > >module, the header files processed over and over. This is very wasteful. > > I think ParcPlaces's ObjectWorks for C++ comes very close to this model > you're proposing. From the very little time I've spent playing with it, > I'm convinced that this is the direction we need to move in... > > -scott This ObjectWorks sounds like something interesting. Can anybody tell me where I can get some information on this or at least how to get in touch with ParcPlace so I can ask them to send me a brochure. -ben aw1r+@andrew.cmu.edu