thanks, Eli 
it was clear from the context that I don't have to release object that  
I got from CFArray 
but I was just curious 
thanks again 

  On Jul 5, 2008, at 12:03 AM, Eli Bach wrote:  
  On Jul 4, 2008, at 8:43 PM, Dmitry Markman wrote:

[...] [...]

[...]

I don't think this is explicitly spelled out anywhere, but for CF  
"constants", such as CFSTR("blah"), kCFBooleanFalse, and other  
constant 'things' like this, there is no real meaning to releasing  
them, but depending on your program's abstraction classes or whatever,   [...]

well I found some information in the NSObject's retainCount method  
documentation: 

"You rarely send a retainCount message; however, you might implement  
this method in a class to implement your own reference-counting  
scheme. For objects that never get released (that is, theirrelease   [...]

Hi
CFGetRetainCount returns 2147483647 (0x7FFFFFFF)  
 what does it mean?  
 CFGetRetainCount documentation doesn't have any info about that
header (CFBase.h) doesn't have any comment  
 thanks  

 Dmitry Markman  
 

Hi folks!

I'm after a little advice - I see people on the list be told "you
shouldn't be doing it like that", so I thought I'd ask _before_ I go
down the wrong route.

Heres the basic idea:
1) I have an IOKit kext that creates IOBlockStorageDriver(s) and device(s). [...]

Dear All,

Having my tool in a single file source.m:


And make file looking like this:


When typing `make`, nothing happens except obj/ directory is being created.

How should GNUmakefile/Makefile look like in order to compile this example?

Mirek Rusin

 [...]

Here's one from the archives: a few years back there was a thread about 
adding direct support for thread-local storage to the OS X toolchain (as 
distinct from pthread support). See the mail below or this archive URL for 
the context: 

   http://lists.apple.com/archives/darwin-dev/2005/Sep/threads. [...]

[...]

I'm not sure I can beat using -Wall, but after the luke warm list  
response I figured I'd 
just dive into the GCC source and find out for myself exactly what was  
going on. 

The short answer, this is behavior is specific to Apple's GCC 4.0.1  
build 5465 (well > 5370, I don't know  [...]