u have any control over CERPCFBundle or influence with the
owners of that, find out why they are throwing NSErrors as exceptions.
Chris Kane
Cocoa Framework, Apple
On May 21, 2011, at 12:34 PM, Ken Victor wrote:
> nick,
> thanx for the reply.
>
> here is a copy of the top portion of t
456-7890"
You're trying to format a number object with NSNumberFormatter and get the
formatter to put junk in the middle of the number [digit sequence].
NSNumberFormatter does not support formats putting junk in the middle of the
number, except for a limited set involving the thousands sep
urprising to that stuff (breaking
assumptions or requirements it has), and possibly surprising to your
app (breaking assumptions or requirements it has). However in this
case, the task death notification, if you need that, requires the
default run loop mode to be run to ge
s are just one thing that can affect readiness.
If you are adding NSOperations to a given queue from multiple threads,
keep in mind that it is very tricky (well, impossible) to accurately
observe from the outside the actual order of events (ie, who got in
first).
Chris Kane
Coc
get those notifications.
That's a separate matter from NSTask, but people may confuse the two
together so I mention it here.
Chris Kane
Cocoa Frameworks, Apple
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post a
[NSLocale systemLocale] returns the root NSLocale.
If you are referring to the BSD/Unix-level locale, you can start by
looking in /usr/include/xlocale.h, but I don't know anything else
about that.
Chris Kane
Cocoa Frameworks, Apple
On Aug 31, 2009, at 12:53 AM, Maggie Zhang wrote:
method, of course,
you don't *need* to pass observer as the context because the observer
is already "self".
Chris Kane
Cocoa Frameworks, Apple
Passing NULL (just, for example) flattens the curve quite a bit.
If you have nothing better to pass in, put this in your
omewhere. And if
it's an important app, we often can't introduce the pool we wanted to
due to binary compatibility, which means everybody loses if it would
have improved typical app performance.
Chris Kane
Cocoa Frameworks, Apple
___
Coco
As of Leopard, you need to do this:
sudo touch /var/log/do_dnserver_log
sudo touch /var/log/dnserver.log
sudo chown daemon /var/log/dnserver.log
as the daemon can't create that file itself in that location any longer.
But you can find the logs in the "system.log" in Console.ap
0
zsh: illegal hardware instruction dead
%
% NSZombieEnabled=YES ./dead
2008-10-30 10:39:35.736 dead[12323:10b] *** -[NSObject self]: message
sent to deallocated instance 0xc048b0
zsh: trace trap NSZombieEnabled=YES dead
Chris Kane
Cocoa Frameworks, Apple
On Oct 30, 2008, at 10:03, Michae
eworks may install
things in the main run loop, but it's possible with other threads as
well.
It boils down to: frameworks are clients of the run loops, just like
the app itself.
Chris Kane
Cocoa Frameworks, Apple
It would seem a little odd... since I would have assumed that only
ap
u are intuiting exactly this when you mention "custom" and
"hidden" input sources.
Try the -run...BeforeDate: method in a conditional loop if you want
block in the run loop most of the time, but want to bail under some
conditions (which would then be the test of the loop).
oPropertyObservingContext;
is this:
static char ABCFooPropertyObservingContext;
and then still using &ABCFooPropertyObservingContext as the context
value. If nothing ends up being packed up tight right after that
char, due to data alignment, well then you still haven't lost anything
map
approximately to one or more new methods or attributes, but you should
use the new methods directly when possible.
setDateStyle: and setTimeStyle: are also 10.4-only. The 10.0 - 10.3
formatter basically had about 3 or 4 methods, only.
Chris Kane
Cocoa Frameworks, Apple
On Jul 15
== 1 - (5 - 1) in
your original computation) is passing an out-of-bounds value with
dateWithComponents:, with who-knows-what effect. It might be well-
defined, it might not be. The result might change between OS
releases. In other words, it seems a bit ambiguous, so best to just
avoid
On Jun 7, 2008, at 6:59, Ricky Sharp wrote:
I will hope though that within the context of say memcpy, that the
GC thread could not collect data. For example, the following
should be safe:
memcpy(myLocalGCAwareBuffer, [data bytes], numberOfBytes);
No. This is equivalent to:
void *tmp0734
16 matches
Mail list logo
