Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!waikato.ac.nz!comp.vuw.ac.nz!gavin Newsgroups: comp.sys.acorn Subject: Re: invoking editors/draw/etc from other app.s Message-ID: <1991Apr11.215337.18049@comp.vuw.ac.nz> From: Gavin.Flower@comp.vuw.ac.nz (Gavin Flower) Date: Thu, 11 Apr 1991 21:53:37 GMT Reply-To: gavin@comp.vuw.ac.nz (Gavin Flower) Sender: news@comp.vuw.ac.nz (News Admin) References: Organization: Dept. of Comp. Sci., Victoria Uni. of Wellington, New Zealand. Keywords: editors, RAMtransfer Nntp-Posting-Host: days.comp.vuw.ac.nz Originator: gavin@days.comp.vuw.ac.nz Lines: 26 Rather than transfer a file - how about allowing the editor to access the memory of the calling application and passing pointers. - This would make for more efficient use of RAM for large files especially with multiple applications in use. Problem: this appears to conflict with the philosophy of giving each application its own "self_contained" address space. Maybe a mechanism similar to the one used by "C" could be used (here the original application is copied to the end of the application space and the new one loaded at the beginning - hohum, this would seem to defeat the object of avoiding multiple copies in RAM...). Essentially I am against having multiple copies of anything in RAM, as a matter of principle (suitable exceptions allowed). -Gavin. -- The main "user" of well brought up, and educated, children is the community at large. So if you really believe in "user pays", charge the correct users - stop overloading parents with financial penalties. ******* These comments have no known correlation with dept. policy! *******