[Top][All Lists]

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

[bug #19099] NSRunLoop: performSelector obj retaining issue (easy to fix

From: Günther Noack
Subject: [bug #19099] NSRunLoop: performSelector obj retaining issue (easy to fix)
Date: Mon, 19 Feb 2007 18:32:08 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv: Gecko/20061025 Firefox/


                 Summary: NSRunLoop: performSelector obj retaining issue
(easy to fix)
                 Project: GNUstep
            Submitted by: guenthernoack
            Submitted on: Monday 19/02/07 at 18:32
                Category: Gui/AppKit
                Severity: 3 - Normal
              Item Group: Change Request
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any



--Quote starts here------------
 * Sets up sending of aSelector to target with argument.<br />
 * The selector is sent before the next runloop iteration (unless
 * cancelled before then) in any of the specified modes.<br />
 * The target and argument objects are <em>not</em> retained.<br />
 * The order value is used to determine the order in which messages
 * are sent if multiple messages have been set up. Messages with a lower
 * order value are sent first.<br />
 * If the modes array is empty, this method has no effect.
- (void) performSelector: (SEL)aSelector
                  target: (id)target
                argument: (id)argument
                   order: (unsigned int)order
                   modes: (NSArray*)modes
--Quote ends here--------------------------

The target and argument arguments should be retained here. (GNUstep
documentation and implementation for this method contradict with Apple's


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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