Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!gate.ready.com!gate.ready.com!ready!buz From: buz@@eng.ready.com (Greg Buzzard) Newsgroups: comp.os.mach Subject: mach_port_allocate_name Message-ID: Date: 24 Jun 91 22:50:07 GMT Sender: usenet@ready.eng.ready.com (Usenet Administrator) Organization: Ready Systems, Smoggyvale CA Lines: 18 What is the reason for the mach_port_allcate_name function being in the kernel interface? It seems to me that all it does (over and above what mach_port_allocate does) is make implementations more difficult. That is, this is the only reason that I can think of that would cause me to use a splay tree in the port name lookup facitily. Similarly, it seems that it would have been nice if mach_port_insert_right was restricted to only insert rights using a "name" that had been previously extracted. Am I missing some implicit rationale for this interface? -- Greg Buzzard internet: buz@eng.ready.com Ready Systems 470 Potrero Ave. phone: 408/736-2600 Sunnyvale, CA 94086