Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!samsung!munnari.oz.au!cs.mu.OZ.AU!cs.mu.oz.au!kre From: kre@cs.mu.oz.au (Robert Elz) Newsgroups: comp.windows.x Subject: Re: Making (Sun) Shared Libraries of Widgets Message-ID: Date: 21 May 91 22:41:05 GMT References: <1991May14.150515.6057@fwi.uva.nl> <9105142329.AA27702@expire.lcs.mit.edu> Sender: news@cs.mu.OZ.AU Organization: Comp Sci, University of Melbourne, Australia Lines: 19 rws@expo.lcs.mit.EDU (Bob Scheifler) writes: >The problem with putting data in the .sa file is that you significantly >increase the number of ways in which binary-incompatible changes can be >made to the library. I don't understand this? Only initialised data that applications will actually reference is generally intended for the .sa file isn't it, not private data in the library. No matter how you change this kind of data its going to lead to binary incompatability and the need to recompile, unless you are very careful in what you do (adding fields to the end of a struct which no-one cares about the size of, etc). >You also need to export a fair number more functions >that could otherwise be static Really? Why? Isn't that the same thing? kre