> I access the window of a view by two different ways, in the controller and in
> the view, resp., and in the controller, I always get a nil pointer.
Have you verified that the view you’re accessing in the controller is the same
instance as the one that works?
___
> - I want to set the displayed contents of V to T2.
>
> What is/are the recommended way/s to do this?
>
> *I would hope that I could assign V.attributedString = T2, but alas the
> world does not seem to be this simple.*
The documentation suggests you should be working with the view’s textStorag
> This discussion about Swift vs Objective-C is interesting, but I think it
> omits something important. Both those languages only build apps for Apple
> products.
This was probably “omitted” because it’s not actually true.
___
Cocoa-dev mailing list (
>> That would be poor API design. If it had -writeToFile, then it would also
>> need -writeToStream:, -writeToFileHandle:, -writeToFileDescriptor:,
>> -writeToNSURLSessionDataDelegate:, etc.
>> Providing the data itself means you can then use existing APIs on other
>> classes to put the data an
he
dispatch_data_t object header. That is not going to match the dispatch_data_t's
actual contents.
--
Greg Parker gpar...@apple.com <mailto:gpar...@apple.com> Runtime
Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.co
d to copy the data.
(Of course, if the code using it as an NSData goes on to call -bytes instead of
-enumerateByteRangesUsingBlock: then it would be forced to copy into a
contiguous representation anyway.)
--
Greg Parker gpar...@apple.com <mailto:gpar...@apple.com> Runtime
Wrangler
_
"
pInfo.orientation = (NSPaperOrientation)NSPortraitOrientation;
#pragma clang diagnostic pop
You should file a bug report against AppKit. I'm not sure there is any benefit
to marking a plain C enum as unavailable. Use of a new enum would work fine
when running on an old
contains
this mCocoaPopupPtr field were itself deallocated then a use-after-free could
cause this symptom.
>> Is there some other way to test for an invalid void pointer?
There is no way to programmatically distinguish all valid Objective-C object
pointers from all invalid ones. It&#x
Casey McDermott wrote:
> NSPanel is still modal, but longer lasting. We use it a lot, and it
> looks better than the modal dialogs in the current app.
I read in digest mode so maybe this has already been pointed out, but NSPanel
is not modal.
___
Coc
> So, to answer my own question, I can "get this to work" using a custom
> NSComboBoxCell
> subclass, implementing -completedString.
>
> Having seen this in action I must confess this is a Bad Idea™.
You’re describing long-standing documented behavior and the correct approach to
achieve the a
, so it may allocate a new
autoreleased string object every time it runs that line.
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator com
> On Dec 4, 2017, at 2:56 PM, Rick Mann wrote:
>
>> On Dec 4, 2017, at 14:55 , Greg Parker wrote:
>>
>>> On Dec 4, 2017, at 2:51 PM, Ben Kennedy wrote:
>>>
>>>> On Dec 4, 2017, at 2:47 PM, Rick Mann wrote:
>>>>
>>>
You can also skip the middleman and use `@kSomeCStringConstant`. After the
preprocessor runs it will be `@"foo"` which the ObjC compiler is perfectly
happy with.
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev mailing
dent of its correctness, the code above *looks* wrong.
That alone is bad. It ought either to call -init or to have a big scary comment
describing why it is safe not to.
* If Foo is ever changed to have a superclass other than NSObject, the code
above is likely to be wrong.
--
Greg Parker
e-language-specific. (The only exception would be if the Swift compiler
> knew that a function was private and final, so it controlled both ends of the
> call.)
The Swift compiler can avoid autorelease more often than that. Swift can use a
simple callee-retain caller-release conve
you if an object is pointed to by some
autorelease pool.
You can call _objc_autoreleasePoolPrint() in the debugger to dump the contents
of the current thread's autorelease pool stack.
You can set environment variable OBJC_PRINT_POOL_HIGHWATER=YES to record stack
traces when a large autoreleas
arising from this reference becoming
> invalid. The most common problem I know of is from table and outline view
> delegate and data source references. In many cases, it’s wise to nil these
> out manually when (say) your window closes.
We prefer to use "unretained" or &q
unting” that might be equivalent.
Deferred reference counting is not much like autorelease. The goal of deferred
RC is to accumulate many retain and release operations from a single thread and
apply them all at once, in the hopes of reducing the cost of repeated refcount
operations on a singl
ug report that this log is too vague.
--
Greg Parker gpar...@apple.com <mailto:gpar...@apple.com> Runtime
Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
> Instead of doing the right thing when shift-clicking (selecting a range from
> the anchor), it simply adds/removes the clicked item to/from the selection.
> That's unlike pretty much any Apple matrix-of-items selection behavior ever.
You mean it selects like Finder icon views have since 1984?
> On Mar 30, 2017, at 9:03 PM, Carl Hoefs
> wrote:
>
>> On Mar 30, 2017, at 8:10 PM, Greg Parker > <mailto:gpar...@apple.com>> wrote:
>>
>>> On Mar 30, 2017, at 7:09 PM, Carl Hoefs >> <mailto:newsli...@autonomy.caltech.edu>> wrote:
&g
f 2 here that it's hard to trust any guess.
Using CFSwapInt64() from CoreFoundation/CFByteOrder.h and from_vax_d8() from
https://pubs.usgs.gov/of/2005/1424/ <https://pubs.usgs.gov/of/2005/1424/>, your
bytes above are:
-41.7215935353
-49.7215935353
-49.7215935353
-49.7215935366
-4
apping is a good hint that you're looking at a PDP-11 / VAX
format. There are two different 64-bit VAX formats, though, and neither is
identical to IEEE even after correcting for the byte order. Simply shuffling
VAX bytes and interpreting as an IEEE double would be misleadingly clos
s your floating-point format unless you have a
collection of known values in both IEEE format and your format. Many of the
historical formats are similar enough that misinterpretation could give
incorrect values that look reasonable by eye.
--
Greg Parker gpar...@apple.com <mailto:gpa
tack frames into your
backtrace which can help identify when +initialize deadlock occurs:
`_WAITING_FOR_ANOTHER_THREAD_TO_FINISH_CALLING_+initialize` and
`_CALLING_SOME_+initialize_METHOD`. Environment variable
OBJC_PRINT_INITIALIZE_METHODS=YES logs some details of +initialize processing
that
itialize checking
is free once you pay the cost of objc_msgSend(). (The ObjC runtime checks
+initialize on uncached dispatch, and never caches anything until +initialize
completes. Most dispatches are cached so they pay nothing for +initialize
support.)
+initialize in Swi
So, apparently iTunes 12.6 doesn't support older plugins any more. Has anyone
seen or heard news of a new SDK so those of us who have created plugins can
update them?
Greg
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not
> call you make might randomly overwrite errno with gibberish.
The POSIX standard specifically states that errno's value is undefined almost
everywhere and can be arbitrarily changed by almost anything.
http://pubs.opengroup.org/onlinepubs/9699919799/functions/errno.html
<http://pubs.o
be reliably enforced even if the student code is stuck in a hang or a loop.
I can't argue with the classification of student code as "hostile" and
"malicious".
--
Greg Parker gpar...@apple.com <mailto:gpar...@apple.com> Runtime
Wrangler
_
e NSDocument would break all of its existing
subclasses.
--
Greg Parker gpar...@apple.com <mailto:gpar...@apple.com> Runtime
Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moder
RL is also recorded in the NSError's userInfo dictionary as
NSURLErrorFailingURLStringErrorKey.
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or mod
an override ought to call [super release] if the object is
expected to be retained and released and deallocated normally.
--
Greg Parker gpar...@apple.com <mailto:gpar...@apple.com> Runtime
Wrangler
> On Jan 25, 2017, at 8:23 AM, Dave wrote:
>
> I hate it when
Dave wrote:
> I hate it when people ask [why are you doing X]!
Decades of experience seeing such questions make us think that when someone is
asking how to do something extraordinary there's about 99% chance they don't
actually need to do it and are making things harder for themselves. Sometime
t operand 0 must use '&' constraint
>
> Is there a way to fix this problem?
You'll get better answers from a clang list such as cfe-us...@lists.llvm.org.
Most of the audience here probably does not have a copy of clang that can
compile PowerPC code.
Why are you using
.
Log or crash in dealloc, if your singleton enforcement might allow the object
to be deallocated and then a new one to be created.
--
Greg Parker gpar...@apple.com <mailto:gpar...@apple.com> Runtime
Wrangler
___
Cocoa-dev mailing list (
ation."
No difference. C static storage with no initializer is always initialized to
zero.
--
Greg Parker gpar...@apple.com <mailto:gpar...@apple.com> Runtime
Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Pl
g.
The deprecation warning told you to use memory_order_relaxed because that is
the memory ordering used by OSAtomicIncrement64.
--
Greg Parker gpar...@apple.com <mailto:gpar...@apple.com> Runtime
Wrangler
___
Cocoa-dev mailing list (Coco
un on 10.11.6 and yet I see these
> message-to-zombie crashes after removing the setDelegate:nil code.
Those crashes are expected.
NSTableView's delegate is zeroing-weak when both of the following are true:
* Your app was built with the 10.11 SDK or newer.
* Your app is running
yMessage]. You must use the result of objc_getClass() instead.
Some "unavailable" classes were in fact present as SPI on older OS versions.
That will confuse tests like `if ([SomeClass class]) { … }`. Test your code on
your old deployment targets.
--
Greg Parker gpar...@apple.com
is generating incorrect code or incorrect debug
> information or corrupting its own indexes. I’ve seen it in my own projects,
> and problems have been reported in the developer forums that sound similar.
> Typically, it appears, cleaning the build folder fixes the problem.
Did
ted, while the other frameworks do. You can force weak linking
> for that particular framework using
>
> -weak_framework AVKit
>
> instead of just using the normal “-framework”.
Please file a bug report. A missing availability at
protocol extensions can solve some of those problems. The protocol
extension provides a default implementation to every class that conforms to the
protocol. Each class may provide its own implementation that overrides the
protocol extension's default implementation.
--
> Does Apple allow a developer to limit the number of devices on which an app
> can run? I have an app that requires you to pay more to install it on more
> than one iPhone and two iPads. It should go without saying these are all on
> the same Apple ID.
>
> I thought Apple didn't allow this. Bu
environment variables then you may be able to use the scan-build tool to run
the clang static analyzer.
http://clang-analyzer.llvm.org/scan-build.html
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev mailing list (C
>> 2. The fact than an object is immutable does not (in general) mean that a
>> copy can be represented by the same object reference. For example, an object
>> that contained its own date of creation might be immutable, but a copy might
>> have a different date, and therefore be a different obje
ion?
My understanding is that this is a limitation of the Xcode build system.
codesign doesn't care about the framework's structure, but Xcode does and it is
telling codesign to look at the wrong path. You should mention rdar://17814234
when you file your bug report.
--
Greg Parke
too easy to accidentally bind to an unrelated superclass ivar when you really
wanted to create a new ivar.
--
Greg Parker gpar...@apple.com <mailto:gpar...@apple.com> Runtime
Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.app
.
>
> Can anybody explain why 3 reboots ≠ 1 reboot?
One possibility: some systems will reset caches or other state if the previous
uptime was too short. This gets you out of reboot loops when a cache gets
corrupted, for example.
--
Greg Parker gpar...@apple.com <mailto:gpa
> I wish to provide a facility with a NSTableView wherein the leftmost
> (specifiable) columns remain statically on the left of the display
> (subject to vertical scrolling) while the remaining columns scroll
> normally constrained to the right of the static columns. I've done
> this succes
> Second question:
> Finder says about the containing folder: 11,239 bytes (33 KB on disk) for 9
> items
> 11,239 = sum of TotalFileSizes of the 8 files in this folder.
> But where do the “33 KB on disk” come from? 8 times “Zero bytes on disk”
> should be zero, shouldn’t it?
Surely "xxx on disk
ven there. On some platforms BOOL is defined as signed char. It may have
any of 254 values other than YES or NO.
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post adm
ent a_bool end up with a 1 value assigned to it?
Don't do that. The behavior is undefined. It will certainly fail on some
current architectures at least some of the time.
You should not use -performSelector:withObject: to call methods that use
non-object parameters.
--
Greg Par
ect that performs the
callback and pass it to the C code to store and call. The block object would
capture the target NSObject so you don't need the dictionary of callback
targets.
--
Greg Parker gpar...@apple.com Runtime Wrangler
_
> On Feb 24, 2016, at 2:31 AM, Dave wrote:
>
> Also, beware subclassing a Non-ARC Class in an ARC Project - you have to have
> the subclass Non-ARC too.
This is not true. For example, NSView is not ARC but you can write ARC
subclasses of it.
--
Greg Parker gpar.
Objective-C++ compilers. Plain C
code is unaffected. Note that you may need code changes if your C code uses
CoreFoundation types and you want to call it from ARC code.
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev
eature(objc_arc)
# error This file must be compiled with ARC enabled.
#endif
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comme
hin an app that doesn't?
Yes, -fno-objc-arc works on iOS too. Was that your question?
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or mod
k: to find
"fifth Saturdays" after some starting date.
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the l
rimary
@interface are @protected by default. Therefore you should either move your
ivars out of the primary @interface, or leave them in @interface but explicitly
declare them @private or @package.
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
> (I also don’t want to restart Xcode wars, but I do actually believe that the
> unified window style that arrived in Xcode 4 was an actual decision about
> which worked best, made by clever people who actually thought about it. It
> wasn’t — I believe — merely clueless. I also want to point out
ith the need to remove
> recent items. No word yet.
> —kevin
While not optimal, I would imagine this could be accomplished with a
combination of recentDocumentURLs, clearRecentDocuments: and
noteNewRecentDocumentURL:.
Greg
___
Cocoa-dev mai
way off. How to fix this?*
What is the value of print(startDate) ?
What do you get if you display `date` and `startDate` using an NSDateFormatter
instead of print() ?
I bet `date` and `startDate` are in fact five minutes apart, but either your
date co
the
Swift-ObjC importer.
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)
> On Nov 10, 2015, at 15:21, Alex Zavatone wrote:
>
>
>> Yeah. Honestly, I'm looking for cases that would justify why all the
>> dictionary object access blocks in this code that use valueForKey are
>> wrapped with @try/@catch clauses. I've never seen cases with objectForKey
>> that would
11-10 10:00:55.296 a.out[38293:4747164] ordinary value
2015-11-10 10:00:55.297 a.out[38293:4747164] (
something,
ordinary,
"@allKeys",
"@something"
)
2015-11-10 10:00:55.298 a.out[38293:4747164] *** Terminating app due to
uncaught exception 'NSUnknownKeyEx
> It's been about 4 or 5 years since I made this mistake but I've just seen a
> massive swath of code where every access of a dictionary object is using
> valueForKey instead of objectForKey.
>
> I've got a few examples of why this is a "really bad idea"™,
I would like to see these examp
27;t match. It is
unlikely that all of the new annotations and all of the documentation are
correct.
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post adm
ny behavior you could imagine.
Lacking the aforementioned concrete example, I can't come up with any of my own
that aren't handled at least as well by a more "normal" mechanism and it
strikes me that this has much more potential for abuse, or at lea
orm was allowed, but I'm not enough of a
language lawyer to know for sure. You might get better answers from a compiler
mailing list.
You can avoid confusion (human and compiler) by writing the statement without
the preincrement's side effect:
ix
> On Oct 5, 2015, at 7:57 PM, Rick Mann wrote:
>
> Especially when a struct can be an AnyObject.
`AnyObject` is an instance of any class type. It is never a struct. `Any`
encompasses both classes and structs.
--
Greg Parker gpar...@apple.com Runtime
gs?
If I recall correctly, you can choose whether or not to relaunch apps when you
deliberately log out or restart, but relaunch is automatic for involuntary
crashes.
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev maili
d by the debugging tools.
(Specifically, it's the machinery that records stack traces of queue
operations.)
If you see this again, please capture a spindump and file a bug report.
After you file the bug report, you might be able to work around it like this:
defaults write com.apple.dt.
g factor, not anything in the runloop or NSTimer itself.
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the
ause it's not optional so Swift won't let it in an 'if
> let'.
selectedRow's "row index or -1" behavior is an obvious candidate for a Swift
optional, but we don't currently have a good way to bridge such API with
Objective-C.
--
Greg Parker gpar..
at the bottom > Add Exception Breakpoint)
Another dumb alternative: implement -[_NSControllerObjectProxy copyWithZone:]
to call abort() or otherwise halt the process. Then it will stop in the
debugger or generate a crash log with a stack trace pointing to the call site.
--
Greg Parker gp
> This toy can connect to the iphone's network by detecting the blinking
> screen of an iPhone. I wonder if it is possible that using this technique
> to transfer data.
Absolutely. Such techniques have been used for 150 years, using lamps or
reflected sunlight to send Morse-like codes to human o
gPropertiesForKeys: nil,
> options:
> .SkipsSubdirectoryDescendants | .SkipsPackageDescendants | .SkipsHiddenFiles)
In Swift 2 this is an OptionSetType. An option set literal looks like this:
[.SkipsSubdirectoryDescendants, .SkipsPackageDescendants, .SkipsHiddenFiles]
--
Greg
you it doesn’t exist any more), so you can’t call it or
> command-click to it.
You should file a bug report. It might be possible to make unavailable
identifiers command-clickable, which would reveal their OS availability range
or their suggeste
> On Aug 21, 2015, at 9:00 PM, Rick Mann wrote:
>
>> On Aug 21, 2015, at 20:58 , Greg Parker wrote:
>>
>>> Rick Mann wrote:
>>>
>>> Also, if the method of the call site is marked as "throws," does that mean
>>> the error wil
> On Aug 21, 2015, at 8:18 PM, Rick Mann wrote:
>
>> On Aug 21, 2015, at 20:06 , Greg Parker wrote:
>>
>>> On Aug 21, 2015, at 6:15 PM, Rick Mann wrote:
>>>
>>>> On Aug 21, 2015, at 18:13 , Quincey Morris
>>>> wrote:
>
ferent: the possibility of error is explicit at
the call site. Some people think this is better (no invisible execution paths)
and some people think it is worse (too noisy). Either way the model is
different enough that we don't call it exception handling.
The fact that Swift's
guarantees.
dispatch_once() is the best solution on Apple's platforms.
If you don't like dispatch_once() then you could use pthread_once().
If you don't like dispatch_once() nor pthread_once() then you can use
PTHREAD_MUTEX_INITIALIZER instead of pthread_mutex_init(). That avoids
where
else later.
The compiler's enforcement is for designated initializers because they should
be a bottleneck that the compiler can see. Enforcing covers of every superclass
convenience initializer would be difficult because it's likely that the
compiler can't see them all when compil
@end
or you can implement it to fail at runtime:
@interface YourSubclass
-(id) init NS_UNAVAILABLE;
@end
@implementation YourSubclass
...
-(id) init {
abort(); // or throw or whatever
}
@end
Either approach wil
subsequent changes. For
example, the code might look like it supports non-ARC but the retain/release
calls are in fact in the wrong places because the only version that is actually
tested is the ARC version.
GC tried the approach of ignoring retain/r
before it is used along all
code paths. The compiler recently became smarter at this analysis so it works
in more cases. (Downside: you must specify the variable's type.)
let myVar: String
if let value = something?.somethingElse {
myVar = value.stringName
} else {
// I have the lot
print("\(c)") // I have the lot
debugPrint(c) // I am CustomDebugStringConvertible
debugPrint("\(c)") // "I have the lot"
Note that (1) string interpolation prefers the non-debug description when
available, and (2) debugPrin
caught up. You should file a bug report.
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators
oryEnumerator. It returns AnyObject type,
> so wouldn't there have to be an NSURL cast in there somewhere?
`for case` uses Swift's pattern matching system, as seen in `switch`. Something
like this should work:
for case let item as NSURL in enumerator! {
…
}
--
Gre
>> If you ask the wrong question, you get a wrong answer. :)
>
> Whether or not it was the wrong question is debatable.
Honestly I find that assertion suspect considering that you've moved the
goalposts three times.
___
Cocoa-dev mailing list (Cocoa-d
lding and packaging embedded dylibs. You
may want to reconfigure your project to use it.
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderato
> On Jul 1, 2015, at 5:39 PM, Rick Mann wrote:
>
>> On Jul 1, 2015, at 17:04 , Greg Parker wrote:
>>
>> Implicitly unwrapped optional is a good solution for this. The source code
>> is no more complicated outside init, and if you get something wrong then you
&g
ally run, and then (2)
cross your fingers really hard.
> It seems the only way to handle this is with an Optional (or implicitly
> unwrapped Optional) type?
Implicitly unwrapped optional is a good solution for this. The source code is
no more complicated outside init, and if you get som
left, bottom, right.
Classic Mac OS was inconsistent. For example, the C struct initializer for Rect
was { top, left, bottom, right }, but the initializer function was
SetRect(&rect, left, top, right, bottom).
--
Greg Parker gpar...@apple.com Runtime Wrangler
__
ld prefer a different whitespace convention, one with no spaces
around the colon in actual parameters. That's a popular convention in
Objective-C. Otherwise there is no difference between Objective-C and Swift
here.
--
Greg Parker gpar...@apple.com Runtime Wrangler
__
mpiler's understanding of the code don't
match.
For example, in your code above, writing `let url: NSURL = …` moves the error
message from the NSURLRequest line to the NSURL line.
--
Greg Parker gpar...@apple.com Runtime Wrangler
_
ou think the caller should be
allowed to specify names or not then you can write two overloads, one of which
simply calls the other. (I did something like this at one point for CGRect's
initializers, allowing any of CGRect(1, 2, 3, 4) or CGRect(x:1, y:2, w:3,
assert() has no
effect on NSAssert().
> Are these set in the Library project or the App project that links to them?
Assert behavior is usually set when the library is compiled. Sometimes the
library will have a runtime variable that affects assert behavior.
--
Greg Parker gpar...@
egateQueue: nil)
You're inside a class func. `self` is the class object for class
HSNDataManager. That class object is not a valid delegate. Presumably you need
to pass an instance of HSNDataManager as the delegate object.
--
Greg Parker gpar...@apple.com Runtime Wrangler
__
wants
NSData. If all goes well you'll get NSData compatibility with zero or one extra
copies.
--
Greg Parker gpar...@apple.com Runtime Wrangler
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests
1 - 100 of 1169 matches
Mail list logo
