Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!att!ihlpf!spock
From: spock@ihlpf.ATT.COM (Weiss)
Newsgroups: comp.windows.news
Subject: references, references, where are those references
Message-ID: <8671@ihlpf.ATT.COM>
Date: 3 Jun 89 21:05:14 GMT
Reply-To: spock@ihlpf.UUCP (Ed-Weiss)
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 37

I have a litewin that contains some buttons.  The following code
runs when one of the buttons is pushed:

	{
		newprocessgroup
		/foo bar send
	} fork waitprocess pop
	/bar null store
	/destroy self send

the /foo method creates an object with its own event manager.
The problem is the window doesn't go away.  There must still
be a reference to it somewhere.  If I make the code look like:

	/foo bar send
	/bar null store
	/destroy self send

the window goes away!  What am I missing?  Where is the extra
reference coming from?  How does forking a process to invoke
the method change things, especially since the process dies?

If I make the code look like:

	{
		newprocessgroup
		(foo) pop
	} fork waitprocess pop
	/bar null store
	/destroy self send

the window goes away.  I'm real confused.
-- 

Ed Weiss	   "I thought it was generally accepted, sir, that
att!ihlpf!spock     vulcans are an advanced and most honorable race."
		   "They are, they are.  And damn annoying at times."