[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #3984] NSConnection registration with same name should not raise ex

From: nobody
Subject: [bug #3984] NSConnection registration with same name should not raise exception
Date: Fri, 04 Jul 2003 01:44:06 -0400
User-agent: Mozilla/4.5 (compatible; OmniWeb/4.2-v435.2; Mac_PowerPC)

=================== BUG #3984: LATEST MODIFICATIONS ==================

Changes by: Richard Frith-Macdonald <address@hidden>
Date: Fri 07/04/2003 at 05:44 (GMT)

            What     | Removed                   | Added
            Severity | 5 - Major                 | 1 - Ordinary
         Assigned to | None                      | CaS
              Status | Open                      | Analyzed

=================== BUG #3984: FULL BUG SNAPSHOT ===================

Submitted by: stefanu                 Project: GNUstep                      
Submitted on: Sat 06/14/2003 at 19:47
Category:  Base/Foundation            Severity:  1 - Ordinary               
Bug Group:  Bug                       Resolution:  None                     
Assigned to:  CaS                     Status:  Analyzed                     

Summary:  NSConnection registration with same name should not raise exception

Original Submission:  If I use [conn registerName:someName] and someName is 
already registered i get an exception. The registerName: method should return 
NO on unsuccessfull registration. Apple docs for registerName says:

Registers the receiver with the default NSPortNameServer under name on the 
local host, returning YES if successful, NO if not (for example, if another 
NSConnection on the same host is already registered under name). 

It is more logical NOT to raise an exception, for example if i want to register 
objects with similar name with a sequence number.

No Followups Have Been Posted

CC list is empty

No files currently attached

For detailed info, follow this link:

  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]