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

[Günther Noack]

URL:
  <http://savannah.gnu.org/bugs/?19099>

                 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

    _______________________________________________________

Details:



--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
documentation.)





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?19099>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/