Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!sunrise.com!astro!samborn From: samborn@sunrise.com (Kevin Samborn) Newsgroups: comp.windows.x Subject: Re: Making (Sun) Shared Libraries of Widgets Message-ID: Date: 3 Jun 91 14:29:17 GMT References: <9105271934.AA23188@expire.lcs.mit.edu> Sender: news@sunrise.com Organization: Sunrise Software International, Newport, RI Lines: 32 In-Reply-To: rws@expo.lcs.mit.EDU's message of 27 May 91 19: 34:51 GMT /\/\ On 27 May 91 19:34:51 GMT, Bob Scheifler said: >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. Bob> It was my misunderstanding that it would be necessary to place Bob> the widget class structures themselves in the .sa part, not Bob> merely the pointers to them. I have been following this, but now I am lost. Finally, at least to clear it up for me, where are you supposed to put the widget class structures? In R4, they were put in the .so part, right? Where do they go now? Does this change the structure of these files? Widget.h WidgetP.h Widget.c Last, if you are just supposed to put a pointer in the .sa part, how is that supposed to look? Just like this?: extern WidgetClass myWidgetClassPointer; Thanks, kevin samborn -- kevin samborn "Anatidaephobia: The fear that somewhere, samborn@sunrise.com somehow, a duck is watching you." ...!uunet!ezx!samborn