On May 9, 2012, at 9:47 AM, koko wrote:
> I wanted to avoid that as the documentation for NSView shows
>
> - (void)print:(id)sender
>
> as the method signature.
IBAction is #def'd as void -- it is just a hook for IB's benefit.
That isn't the problem.
More likely than not, your view isn't
On Nov 10, 2011, at 6:03 PM, Don Quixote de la Mancha wrote:
> I don't have a problem with the system killing runaway processes.
> What I have a problem with is that calloc() NEVER returns NULL. If it
> ever did, I would have plenty of opportunity to deallocate ALL of the
> memory I just allocat
On Sep 12, 2011, at 10:27 AM, lbland wrote:
> What does the 98 at the end of this line mean:?
>
> 8 com.apple.CoreFoundation 0x7fff90662d32 -[NSMutableArray
> removeObjectsInRange:] + 98
>
>
> … all the tech notes I can find explains everything else, but neglects
> describing
On May 17, 2011, at 9:54 AM, Bing Li wrote:
> But I noticed that Cocoa threading provides wait/pulse-like synchronization
> techniques, such as Condition. I believe these techniques can be used to
> control a thread which has a while-true loop. So I think RunLoop can be
> replaced. Do you thin
In short, do **not** poll. Not ever.
If you are doing something like this:
while (stillDontGotIt) {
sleepForAMomentAndHopeWeGetIt();
}
(or the obvious spin-and-try-lock variant).
Then you are doing it wrong.
It eats CPU, makes your app less responsive, eats batte
> Am 01.04.2011 um 18:38 schrieb James Bucanek:
>
>> So I'm going with plan B, which is create a custom CALayer that draws a
>> single spinner "wheel" image and then rotate it using a key-frame animation.
As long as you don't actually show rotation of the lines of the progress
indicator, that'
On Mar 8, 2011, at 12:33 AM, Bruno Causse wrote:
> the performance is not a problem, all my threads are waiting for a answer to
> a request.
That is potentially still a big problem as every thread uses kernel resources,
reserves memory for a stack, and otherwise pollutes the kernel's schedulin
On Mar 7, 2011, at 12:27 PM, Bruno Causse wrote:
> hi all,
>
> how many NSThread i can create?
Quite a few more than are useful, performant, or optimal...
b.bum
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin reques
On Feb 11, 2011, at 1:16 PM, Joanna Carter wrote:
> I would totally agree that it is a phenomenally powerful concept, giving just
> the kind of functionality I was originally looking for, as a replacement for
> method pointers. I will be using it as soon as I find a need that warrants it.
>
>
On Nov 23, 2010, at 5:41 PM, Rob Ross wrote:
> otherwise you are not responsible and
More or less (there are some exceptions).
> the object will be auto-released."
Sometimes.
[NSString stringWithString: @"Foobar"];
[NSNumber numberWithInt: 7];
Typically returns an object that is not
On Nov 18, 2010, at 2:34 PM, John Engelhart wrote:
> method is just going to -dealloc my object and do something else (you know,
> basically exactly what I'm trying to do with my own object substitution, hint
> hint), then what's the point in even trying to do object substitution in the
> firs
On Nov 18, 2010, at 1:10 PM, John Engelhart wrote:
> The basic premise behind self = [super init...] is that the "lower levels of
> initialization are free to return a different object than the one passed in".
>
> However, there is an unstated assumption in this reasoning: whatever object
> is
The issue [I'd bet -- don't have time to dive deep] is that you don't have a
strong reference to the Tasker instance.
Since notification observers don't hold strong references to observers, either,
the garbage collector sees Tasker as garbage and collects it.
You could fix this any number of wa
On Oct 28, 2010, at 9:16 AM, Jonny Taylor wrote:
>> Note that sending notifications to other threads while holding locks in the
>> current thread (or queue) is rife with danger & fragility. It is great way
>> to create deadlocks and, if not, to end up with a solution that has all the
>> mainte
On Oct 28, 2010, at 7:01 AM, Jonny Taylor wrote:
> I currently have a property declared as follows:
> @property(atomic, readwrite, retain) MyFrame* latestFrame;
>
> When the value is set, I would like to broadcast a notification on the main
> thread, and one way of doing that would be to write
On Oct 26, 2010, at 12:42 PM, Sean McBride wrote:
> And presumably objc_unregisterThreadWithCollector() at the end of your
> thread's function... yes?
Yes; it'll happen automatically on thread death, effectively.
Registering/unregistering a thread on the fly isn't really something that is
On Oct 25, 2010, at 2:22 PM, Andy O'Meara wrote:
> Per Apple GC Programming Guide (page 15):
>
> // SNIP //
>
> Garbage collection is performed on its own thread--a thread is explicitly
> registered with the collector if it calls NSThread's currentThread method (or
> if it uses an autorelease
On Oct 18, 2010, at 8:33 PM, Gerriet M. Denkmann wrote:
> First of all: Thank you very much for this very helpful article.
>
> I just created a new Cocoa Document based app in Xcode (Version 3.2.4).
> I did not edit any of the Xcode supplied files.
> Clicked Build and then Run with Performance T
On Oct 18, 2010, at 8:42 AM, Matt Gough wrote:
> Perhaps Apple should aim Instruments at itself. Inspired by Bill's post, I
> just did a HeapShot test on my own app. Instruments went up to 2.5GB real Mem
> and stayed at that when I closed the Instrument window.
"2.5GB Real Mem" is relatively m
Folks--
I wrote up an article on how to use the "Mark Heap" / "Heapshot
Analysis" tools in Instruments to detect, analyze, and fix memory leaks,
including those that leaks can't find.
http://www.friday.com/bbum/2010/10/17/when-is-a-leak-not-a-leak-using-heapshot-analysis-to-fin
On Oct 16, 2010, at 11:46 AM, Dave DeLong wrote:
> You can save the NSThread instance in an ivar (after alloc/init'ing it), and
> then use all the NSThread methods to figure out what to do. (Don't forget to
> -start the thread when you're ready to kick it off)
A far better solution, though, w
On Oct 15, 2010, at 12:00 PM, Hank Heijink (Mailinglists) wrote:
>> NSString *theScannedString;
>
> I would set theScannedString to nil here to avoid your crash below.
That would be making the assumption that the implementation of
scanCharactersFromSet:intoString: does not muck with the pointe
On Oct 10, 2010, at 10:20 AM, Bill Bumgarner wrote:
> On Oct 10, 2010, at 5:10 AM, Jerry Krinock wrote:
>
>> In deciding how to solve the problem, I'd like to know how gcc solved the
>> problem! It seems there are three choices:
>>
>> (1) Wrap my non-atomi
On Oct 10, 2010, at 5:10 AM, Jerry Krinock wrote:
> In deciding how to solve the problem, I'd like to know how gcc solved the
> problem! It seems there are three choices:
>
> (1) Wrap my non-atomic custom setter/getter code to make it atomic.
> (2) Change my declaration to make it nonatomic.
>
On Oct 8, 2010, at 5:27 PM, Rick Mann wrote:
> Hmm...thinking about it a bit more...how do dynamically-synthesized property
> ivars work (where you just @synthesize them without declaring an ivar)? Do
> they use class_addIvar()? That suggests I'm wrong about class layout.
It be compilation tim
On Oct 8, 2010, at 11:52 AM, Kyle Sluder wrote:
> Using GCD:
>
> id myObj;
> dispatch_sync(dispatch_get_main_queue(), ^{ myObj = CreateTheObject(); });
__block id myObj;
> dispatch_sync(dispatch_get_main_queue(), ^{ myObj = CreateTheObject(); });
___
On Oct 7, 2010, at 10:26 PM, Rick Mann wrote:
> The doc says that property_getName() returns a C string, but doesn't specify
> the encoding. I would like to work with the property name as an NSString, but
> I can't really make one without knowing the encoding.
Assume UTF8 (really, ASCII) for n
On Sep 19, 2010, at 1:11 PM, Markus Spoettl wrote:
> One thing you get is automatic KVO change notifications. When you set a
> property through its setter, you don't have to use -willChangeValueForKey:
> and -didChangeValueForKey: in order to trigger -observeValueForKeyPath:
> messages for tho
On Sep 14, 2010, at 7:34 AM, Jonathan Guy wrote:
> I was under the impression that if you compile GC in supported mode it was
> capable of loading code with or without GC? I'm a bit confused as to why this
> is happening. Can any GC gurus out the shed any light?
Everything in an application mu
On Sep 9, 2010, at 4:27 AM, Luca C. wrote:
> 0 libobjc.A.dylib 0x7fff8766c11c objc_msgSend + 40
> 1 com.apple.CoreFoundation 0x7fff882e9cc6
> _CFAutoreleasePoolPop + 230
> 2 com.apple.Foundation 0x7fff87a4881a
Classic overrelease problem.
On Aug 20, 2010, at 2:33 PM, Gregory Weston wrote:
> Bill Bumgarner wrote:
>
>> Preference panes are not designed to be embedded into applications other
>> than the System Preferences application. Even if you were to make it work
>> (which would require duplica
On Aug 20, 2010, at 3:44 AM, Jon Guy wrote:
> Hi
> I'm trying to embed a couple of the system pref panes into an app by
> following the Apple documented method, here's basically whats going on:
>
> NSBundle *bundle = [NSBundle
> bundleWithPath:@"/System/Library/PreferencePanes/SharingPref.pref
On Aug 10, 2010, at 9:12 AM, Alastair Houghton wrote:
> That said, is the part about objects escaping zones really true for *NS*Zone?
> It's true for malloc zones, for sure, but the docs for NSRecycleZone say:
>
> Frees zone after adding any of its pointers still in use to the default zone.
>
On Aug 10, 2010, at 1:31 AM, Alastair Houghton wrote:
> Sounds like a bug to me. While zones are *discouraged* (they're very
> definitely an advanced topic and easily misused), I don't think they're
> actually deprecated.
Their use is deprecated and should be documented as such.
Zones wer
On Jul 26, 2010, at 1:39 PM, k...@highrolls.net wrote:
> What should the launchPath be for [NSTask setLaunchPath:path] ? ?usr/bin/rm
> is not valid i.e. where is rm?
Why use a task to remove a file?
Use NSFileManager's APIs.
b.bum
___
Cocoa-dev m
On Jul 14, 2010, at 10:50 PM, Michael Link wrote:
> and I use a KVC method to access the value of foo (e.g.
> [object valueForKey:@"foo"];
>
> is it still accessed atomically?
Yes.
b.bum
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Pleas
On Jul 7, 2010, at 11:33 AM, Matt Neuburg wrote:
> On or about 7/7/10 11:17 AM, thus spake "Bill Bumgarner" :
>
>> I missed the OP's post
>>
>> If the static analyzer is barfing up a false positive, please report it
>> (http://bugreport.apple.
I missed the OP's post
If the static analyzer is barfing up a false positive, please report it
(http://bugreport.apple.com/ works fine).
b.bum
On Jul 7, 2010, at 10:34 AM, Matt Neuburg wrote:
>> Maybe I should report this to the LLVM team?
>
> You can, but I wouldn't get my knickers in a
On Jun 28, 2010, at 3:20 PM, Dave DeLong wrote:
> Except that the Short Practical Guide to Blocks you linked to uses:
>
> ^ () { };
That is a typedef form, not the block literal form.
Wee fun.
BOOL (^blocksOfFun)(int) = ^ BOOL (int x) {
return x % 3;
};
for(int i=0;
. The whole idea was to stick to a format
> that had precedence but use the new symbol ^(only remaining operator that is
> not overloadable in C++) instead of *(btw, that wasn't a block with a void
> return type :-).
>
> Anyhows, I no longer think this is a cocoa questio
On Jun 28, 2010, at 1:45 PM, Michael Ash wrote:
> But I was unable to find any discussion of HOW you explicitly declare
> the return value of a block expression.
^ () { };
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post ad
On Jun 26, 2010, at 11:09 PM, Tony Romano wrote:
> - (void)_copyOrMoveURLs:(SEL) s opMove:(BOOL)op src:(NSDictionary *)URLs
> completionHandler:(void (^)(NSDictionary *newURLs, NSError
> *error))handler
> {
>
> __block char array1[5];
> array1[0] = 'W';
>
>
>
On Jun 26, 2010, at 9:14 PM, Tony Romano wrote:
> That's why I asked for an example of what the op question is
http://lists.apple.com/archives/cocoa-dev/2010/Jun/msg01040.html
> This would seem to imply that a __block variable *can* be a *fixed* length
> array. But when I try to write into such
On Jun 26, 2010, at 8:56 PM, Kyle Sluder wrote:
> Putting __block variables inside of blocks is completely pointless.
> The purpose of the __block qualifier is to mark variables in the
> enclosing scope to be copied into the block.
Unless you have a Block within the Block and you want to share a
On Jun 26, 2010, at 7:48 PM, Tony Romano wrote:
> hmmm. Your saying this doesn't work?
>
> NSBlockOperation * foo = [NSBlockOperation
> blockOperationWithBlock:^{
> __block char array1[5];
>
> array1[0] = 'T';
> }];
>
>
On Jun 26, 2010, at 6:38 PM, Matt Neuburg wrote:
> The docs say: "There are two further restrictions on __block variables: they
> cannot be variable length arrays, and cannot be structures that contain C99
> variable-length arrays."
>
> This would seem to imply that a __block variable *can* be a
On Jun 18, 2010, at 12:09 PM, Tony Romano wrote:
> First, the objects are retained by dispatch_async as others have mentioned.
> Second, I'm not sure why you used 2 queues for the tasks in your code, seems
> overly complex. Async queues are serialized, which means that you can
> continue to
On Jun 17, 2010, at 5:37 AM, Alexander Spohr wrote:
> But I think you want to know what the va_list contains.
> Then you just loop over it.
> "man stdarg" will help.
>
> Example:
> void foo(char *fmt, ...)
> {
> va_list ap;
> int d;
>
On Jun 2, 2010, at 2:16 PM, jonat...@mugginsoft.com wrote:
> My app is ObjC cocoa based
>
> It also loads and executes PyObjC classes.
>
> I require my loaded PyObjC code to access an ObjC class (myControllerClass)
> defined within an ObjC framework linked to the main application.
>
> The de
On May 7, 2010, at 11:34 AM, Patrick M. Rutkowski wrote:
> Will NSObject's init method ever really return nil?
>
> E.g. if I sub-class NSObject, then is it worth checking for nil after
> doing self = [super init]?
>
> I know there are many classes in UIKit and Cocoa which most definitely
> can
On May 5, 2010, at 1:13 PM, Kyle Sluder wrote:
> It tests the code that was built for the simulator. See here for more
> information:http://developer.apple.com/iphone/library/documentation/Xcode/Conceptual/iphone_development/135-Unit_Testing_Applications/unit_testing_applications.html
What Kyle
On May 4, 2010, at 11:26 PM, Csaba Trucza wrote:
> As far as I know the otest unit testing application runs as a command line
> tool (so I assume it is a Mac OS X application) and somehow manages to load
> the iPhone bundles.
>
> Any ideas?
otest doesn't load the bundle at all.
It examines the
On Apr 28, 2010, at 10:35 AM, Jens Alfke wrote:
> SQLite works fine with multiple clients — it uses file locking to support
> transactions and ACID properties. I’ve used it that way myself. It just
> doesn’t scale as well as a full server-based system, because doing locking
> via the filesyste
On Apr 27, 2010, at 3:05 PM, Uli Kusterer wrote:
> On 27.04.2010, at 23:22, Gary L. Wade wrote:
>> Calling -retainCount
>> immediately before and after the -setDelegate call is pretty much the only
>> way.
>
> Nope. It'll only lead to pain and suffering. And false positives. What if
> setDelegat
On Apr 27, 2010, at 2:09 PM, Gary L. Wade wrote:
> On 04/27/2010 1:58 PM, "Bill Bumgarner" wrote:
>
>> Frankly, the -retainCount method should be deprecated and, eventually,
>> removed.
>
> I wouldn't go THAT far; after all, when you're tracking a m
On Apr 27, 2010, at 1:49 PM, Bill Appleton wrote:
> it's too bad this is unreliable
>
> an object should be able to return this info
An object does return this info, the problem is that the # is a meaningless
internal implementation detail of the Cocoa frameworks.
For example, if you create a
On Apr 15, 2010, at 8:50 AM, Henrietta Read wrote:
> What's the correct way to open a text file? I'm using:
>
> NSError *error = nil;
> NSStringEncoding encoding;
>
> [myMutableString setString:[NSString stringWithContentsOfFile:filePath
> usedEncoding:&encoding error:&error]];
>
> but o
On Apr 8, 2010, at 10:21 AM, Patrick M. Rutkowski wrote:
> Agreed, but there's always the danger the +array method, which might
> actually be implemented in NSArray.m, will not properly initialize the
> more specific NSMutableArray object.
>
> Of course, in this specific case that's the case, bu
On Apr 8, 2010, at 7:35 AM, Patrick M. Rutkowski wrote:
> What I was worried about is that maybe NSMutableArray (or any
> sub-class in general) would need to do some special sub-class-specific
> initialization, which it might not have implemented. I guess though,
> if you're going to be sub-class
On Mar 11, 2010, at 11:15 AM, Andrew James wrote:
> Does Cocoa have sorted containers so that an object can be inserted in sorted
> order? If so it seems like this would be far less expensive.
Depends entirely on need. Keeping a container sorted on insert can be quite
expensive; potentiall
On Mar 11, 2010, at 8:58 PM, Gideon King wrote:
> So as long as you are careful about what you do, yes it is entirely possible
> to replace methods at will. I hope nobody misuses it, but it certainly was
> essential in my debugging - yes, I found it! Yay!
Where "careful about what you do" inc
On Mar 8, 2010, at 7:44 PM, Philippe Sismondi wrote:
> if(![super init])
> return nil;
Since no one else mentioned it in the followups, the above is wrong. This is
correct:
self=[super init];
if (!self)
return nil;
... etc ...
b.bum
_
On Feb 23, 2010, at 8:57 PM, Steve Christensen wrote:
>> That code uses blocks, though, which implies that it will be compiled using
>> a later version of Objective-C. Will that code really run on older versions
>> of OS X?
>
> The compile-time conditional assumes that you're building against
Folks-
I finally banged out part IV -- the 'slow path' & odds/ends -- of my
tour of objc_msgSend() on x86_64. If you want to know how method invocations
works in instruction by instruction detail on x86_64, you might find it
interesting:
http://www.friday.com/bbum/2009/12/18/o
What Kyle and Jens said, but there is one particular cardiac action impaired
horse that I wanted to flog...
On Feb 3, 2010, at 8:30 AM, McLaughlin, Michael P. wrote:
> I thought that this should all be correct but somehow it crashes, at times
> immediately, at other times only when everything is
On Jan 29, 2010, at 4:09 AM, Jonathan Guy wrote:
> Thanks Greg. It was indeed a category issue but I seem to have fixed one
> problem and found another. If I load the first bundle, make a method call,
> then immediately unload, load the second bundle and make the same function
> call (all in t
> On Jan 10, 2010, at 4:01 PM, Paul Sanders wrote:
>> It would be extremely simple for Apple to implement this
>> suggestion and there's no question in my mind that it would
>> rapidly nail a certain class of bug, so what's to lose?
>
> Famous last words ;)
All snark aside, I wrote a weblog
On Jan 10, 2010, at 4:01 PM, Paul Sanders wrote:
> It would be extremely simple for Apple to implement this
> suggestion and there's no question in my mind that it would
> rapidly nail a certain class of bug, so what's to lose?
Famous last words ;)
b.bum
On Jan 10, 2010, at 10:29 AM, Glenn L. Austin wrote:
> If Instruments didn't crash on launch of our app, it would have been very
> helpful. I use it for my own projects (which aren't quite as large), but it
> wasn't available for this case.
malloc_history and MallocStackLoggingNoCompact would
On Jan 4, 2010, at 1:39 PM, jonat...@mugginsoft.com wrote:
> How can a multiple stack root occur?
> Is this just saying that the same object is referenced by multiple stack
> allocated pointers at the time that the sample was taken?
That is correct; the object may be referenced by multiple loc
On Jan 4, 2010, at 11:50 AM, jonat...@mugginsoft.com wrote:
> A recent post mentioned the concept of GC memory leakage.
>
> How is is this defined? Is it merely a failure to nil out a rooted reference?
>
> man heap(1) makes reference to over-rooted objects.
> Are these merely objects with more
On Jan 4, 2010, at 5:31 AM, Quincey Morris wrote:
> On Jan 3, 2010, at 18:21, Ben Haller wrote:
>
>> Bill, I for one would like to hear a bit more about this. What has changed
>> in SL? Why would it ever be possible to outrun the collector? If the limit
>> of memory is being reached, can't
On Jan 3, 2010, at 2:45 PM, Graham Cox wrote:
> On 04/01/2010, at 4:59 AM, Michael Abendroth wrote:
>
>> When I write something like:
>>
>> while (true) {
>> NSString *s = [[NSString alloc] initWithString:@"applejuice"];
>> }
>>
>> Will s be garbage collected? If not, how can I make sure it d
On Jan 3, 2010, at 9:59 AM, Michael Abendroth wrote:
> When I write something like:
>
> while (true) {
> NSString *s = [[NSString alloc] initWithString:@"applejuice"];
> }
>
> Will s be garbage collected? If not, how can I make sure it does get
> deallocated by garbage collection.
I'm not en
On Dec 30, 2009, at 9:08 AM, Helen Cooper wrote:
> [self performSelector:@selector(doSomething00) withObject:NULL
> afterDelay:4.0];
>
>
> -(void)doSomething00{
> [someDelegate doSomething];
> }
>
> I am wondering though, if there might be a way to use
> performSelector:withObject:afterDela
On Dec 26, 2009, at 9:38 AM, Richard Somers wrote:
> Objects in a persistent store are unordered. If I fetch the objects, change
> nothing in the store, then fetch them again, do the two fetches give me the
> objects in the same order?
Maybe. Behavior is undefined.
b.bum
__
On Dec 22, 2009, at 11:49 PM, Franck Zoccolo wrote:
> You said that you're using garbage collection. When using GC retain and
> release messages do nothing, and the retain count is not used to
> determine when an objet can be freed from memory.
If -retainCount is returning 1, then he can't be us
On Dec 22, 2009, at 9:40 PM, Michael Craig wrote:
>NSLog(@"Reference count: %lx", (unsigned long) [converter retainCount]);
>[converter release];
>NSLog(@"Reference count: %lx", (unsigned long) [converter retainCount]);
If the -release is going to deallocate converter, then the subse
On Dec 22, 2009, at 11:19 AM, PCWiz wrote:
> Is there any easy way to execute a portion of code on the main thread without
> going through the mess of delegates and selectors?
Delegates have *nothing* to do with main thread execution. Selectors a bit
orthogonal, too.
If you want to execute
On Dec 10, 2009, at 11:55 PM, Parimal Das wrote:
> I must be missing something here.
> Can anyone point what is wrong here.
(1) there is no need for an autorelease pool in such a simple -awakeFromNib.
It will be in the context of an autorelease pool to begin with and doesn't
create enough mem
On Dec 3, 2009, at 8:10 AM, gMail.com wrote:
> Thanks. I supposed that I was loading from the cache. It's a pity.
> It was too nice to load 10,000 files x 4KB each, in only 1.2 secs.
> Maybe one day, when I will be not longer on this planet :-)
> Just to mention I run MacOSX 10.6.2 and I build ag
There seems to be some confusion as to what the 8GB limit under GC means. So,
a clarification
The 8GB limit is only on GC based allocations. That is, your app can allocate
up to 8GB of GC'd allocations, no more.
There is no such limit on the other allocation zones (the malloc zone, for
e
On Dec 2, 2009, at 1:01 PM, Sean McBride wrote:
> If GC memory is really limited to 8 GB (and not 32), then I probably am
> hitting that limit with the guard pages on. :( Is there a way to
> increase that limit, at least in debug? 8 is pretty puny. :(
Grab the source. It is just a constant.
On Dec 2, 2009, at 12:24 PM, Greg Parker wrote:
> The 64-bit garbage collector reserves a 32 GB heap and will not expand it
> further. If you allocate more than 32 GB you'll run out of memory.
Actually, it is an 8GB heap.
b.bum
___
Cocoa-dev mailing
On Nov 30, 2009, at 12:50 PM, Dennis Munsie wrote:
> Not that I'm advocating it, but you can also declare a field as @public to
> allow you to access it via the -> operator. Of course, I could be missing
> some compiler magic going on behind the scene as well, and it may not
> actually be the
On Nov 29, 2009, at 4:21 PM, Oftenwrong Soong wrote:
> What exactly is this @defs keyword supposed to do?
It effectively turned an Objective-C class declaration into a standard C
structure such that you could access the instance variables directly via a
simple -> operator. Was mostly used fo
On Nov 28, 2009, at 5:02 PM, William Squires wrote:
> SCDynamicStoreRef
> SCDynamicStoreCreate (
> CFAllocatorRef allocator,
> CFStringRef name,
> SCDynamicStoreCallBack callout,
> SCDynamicStoreContext, *context
> );
>
> Here's where my confusion begins.
Did you read the documentation for
On Nov 27, 2009, at 5:08 PM, Mr. Gecko wrote:
> My idea was to basically write a module that runs NSTask to start the cocoa
> binary and just have a framework to like manage the server information and
> talk to the module, by printf I guess, saying like which headers to return
> and the data s
On Nov 27, 2009, at 4:30 PM, Mr. Gecko wrote:
> Well I'm wanting to be able to write image generators and other things that
> is near impossible to do in php or any other web scripting language, also
> running compiled source is faster then a script. My idea is to write a module
> so I can jus
On Nov 8, 2009, at 5:47 AM, Shai Shasag wrote:
> How could this be? I think the problem is that both bundle_A & bundle_B have
> principle class with the same name. Somehow Cocoa gets confused.
No "somehow" about it. Objective-C does not support namespaces; all classes
(and selectors) exist wi
On Nov 2, 2009, at 2:17 AM, Jim Kang wrote:
> I seem to be able to use NSInvocation to execute methods that have
> parameters are pointers, like NSString* or NSDictionary*, but when I try to
> invoke a method with a parameter that is not a point, like this -
>
> (void)methodWithCGPoint: (CGPoint)
Related, I recently ported a handful of [really ancient NeXTSTEP] screensavers
to Snow Leopard, including the ability to run on both 64 bit GC'd and 32 bit
non-GC'd Snow Leopard or Leopard (ppc or i386).
http://www.friday.com/bbum/2009/10/19/spiroscales-source-for-snow-leopard-available/
http://
On Oct 27, 2009, at 3:08 PM, Sean McBride wrote:
> nor do I do any dynamic
> loading nor unloading of bundles.
You don't, but there appear to be certain QuickTime components --
decoder/encoder modules, perchance? -- that do and will inside your application
if you use QuickTime. There may be o
On Oct 27, 2009, at 10:43 AM, Sean McBride wrote:
> Occasionally, my GC app crashes in objc_msgSend with none of my code in
> the backtrace. This only happens to customers; I've never caught it in gdb.
>
> I've read through Greg's awesome "So you crashed in objc_msgSend()"
> article, but I stil
On Oct 23, 2009, at 8:40 AM, Nick Rogers wrote:
> Thanks for the reply.
> The app actually works as a launcher of another app with root privileges (its
> only job is this).
> Hence its a standard cocoa project with the following frameworks:
> CoreFoundation, Cocoa, AppKit, CoreData, Foundation a
On Oct 23, 2009, at 5:04 AM, Nick Rogers wrote:
> I compiled using Xcode3.2 on 10.6.1, 10.5 base sdk and for Intel 64-bit only
> with GC only option.
> The program compiles fine, but the following error is there when launching it
> on 10.5.8 system: (window doesn't appear)
>
> EXC_BREAKPOINT (
On Oct 22, 2009, at 5:54 AM, Jim Kang wrote:
> However, a selector is not a string. I was just listening to this podcast
> with Mike Ash, and he discusses this around the 9:23 mark or so:
>
> http://podcast.mobileorchard.com/episode-23-mike-ash-on-the-objective-c-runtime-objects-and-the-runtime-
On Oct 21, 2009, at 1:39 AM, Nick Rogers wrote:
> (gdb) info gc-roots 0x2004f9340
> Number of roots: 1
> Root:
> 0 Kind: bytes rc: 1 Address: 0x000200543b40 Offset:
> 0x0008
> 1 Kind: object rc: 0 Address: 0x0002004f9340 Class: Volume
>
> Is there a retain cyc
On Oct 21, 2009, at 7:45 AM, Fritz Anderson wrote:
> Does this mean that there's a race between the NIB loader's need to create a
> strong reference and the GC thread's imperative to collect the object before
> it is referenced?
No; the objects are strongly referenced by stack or by the de-ar
On Oct 17, 2009, at 8:38 AM, BJ Homer wrote:
But assuming that you
wanted it there in the first place, why does the GC version not need
the
synchronization?
Under GC, object reference assignments -- scanned pointer assignments,
technically -- are, in and of themselves, atomic. Note that
1 - 100 of 530 matches
Mail list logo
