Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!ukma!seismo!beno!black From: black@beno.CSS.GOV (Mike Black) Newsgroups: comp.sys.amiga.programmer Subject: Re: Message Ports Keywords: ports CreatePort Message-ID: <49659@seismo.CSS.GOV> Date: 26 May 91 14:11:23 GMT References: Sender: usenet@seismo.CSS.GOV Distribution: comp Organization: Center for Seismic Studies, Arlington, VA Lines: 20 > >That solution is kind of gross, but then again I don't think ports >were meant to hang around after a program exited. Do you really need >a port that lasts after your program's termination, or was this just >for the test program? > Ports tie themselves to the invoking task and therefore are definitely NOT meant to hang around after termination. His program works just fine if modified slightly so that it hangs around for a while after creating the port so you can run the program from another window to try and find it (WITHOUT deleting it). Always let the program that creates the port delete it. Mike... -- ------------------------------------------------------------------------------- : usenet: black@beno.CSS.GOV : land line: 407-494-5853 : I want a computer: : real home: Melbourne, FL : home line: 407-242-8619 : that does it all!: -------------------------------------------------------------------------------