On Jun 4, 2009, at 5:39 AM, harpreet_si...@oxyent.com wrote:
Hello All,
I am facing an issue in use of mach_absolute_time().
mach_absolute_time() gives drift even when NTP timing update is on.
sleep(5);
Your assuming that sleep() provides drift free timing, which it does
n
On Thu, Jun 4, 2009 at 8:39 AM, wrote:
> I am facing an issue in use of mach_absolute_time().
Your post is off-topic in two ways: First, this has nothing to do
with the thread to which you replied (start a new thread for a new
question/topic). Second, this has nothing to do with Cocoa at all
Hello All,
I am facing an issue in use of mach_absolute_time().
mach_absolute_time() gives drift even when NTP timing update is on.
Please see my code below:
#import
#import
nt main(int argc, char *argv[])
{
uint64_t nowTime = mach_absolute_time();
uint64_t drift = 0;
On 04 Jun 2009, at 14:31, Steven Hamilton wrote:
Hi folks,
I need some advice on how best to handle an itchy problem. In order
to tighten up my coding I'm compiling with warnings as errors which
has showed up a big problem with my code.
I have a tableView using a datasource array of dicti
On 04/06/2009, at 10:36 PM, Graham Cox wrote:
On 04/06/2009, at 10:31 PM, Steven Hamilton wrote:
I'm getting the error because I initially declared my credit and
debit objects as NSNumbers. Can I recast them without them losing
scope?
Yes, just do this: credit = (id)[NSNull null];
--G
On 04/06/2009, at 10:31 PM, Steven Hamilton wrote:
I'm getting the error because I initially declared my credit and
debit objects as NSNumbers. Can I recast them without them losing
scope?
Yes, just do this: credit = (id)[NSNull null];
--Graham
_
Hi folks,
I need some advice on how best to handle an itchy problem. In order to
tighten up my coding I'm compiling with warnings as errors which has
showed up a big problem with my code.
I have a tableView using a datasource array of dictionaries. Fairly
standard stuff. 2 of the keys in t
On Oct 11, 2008, at 3:26 PM, Seth Willits wrote:
Note that nowhere in there is there anything related to how many
arguments there are, or what type they are.
Ahh. I guess I mis-remembered varargs. I thought they did have a
count. I'm
You can tell how often I've had to use it ;-)
Nope --yo
On 10/10/08 5:58 PM, Seth Willits said:
>You can't stick nil into dictionaries and arrays. So either you stick
>an empty string, an NSNumber with 0, etc if those are OK, or you can
>use NSNull.
Or you can use NSPointerArray (on 10.5+).
--
_
On Oct 11, 2008, at 11:47 AM, Michael Ash wrote:
On Sat, Oct 11, 2008 at 1:57 PM, Seth Willits <[EMAIL PROTECTED]>
wrote:
If it's what I think you're talking about then: No, nil is used as
a marker
for the variable argument list to say "this is the end of the
list." It's
not actually insert
On Sat, Oct 11, 2008 at 2:58 AM, Seth Willits <[EMAIL PROTECTED]> wrote:
> On Oct 10, 2008, at 5:40 PM, Ian Joyner wrote:
>
> I'm just trying to work out what NSNull really is in the Cocoa context. Is
>> it an object in Cocoa?
>>
>
>
> As I said, yes. It's truly an object. (A singleton, as well.)
On Sat, Oct 11, 2008 at 1:57 PM, Seth Willits <[EMAIL PROTECTED]> wrote:
> If it's what I think you're talking about then: No, nil is used as a marker
> for the variable argument list to say "this is the end of the list." It's
> not actually inserted into the dictionary at all. Why it's required is
On Sat, Oct 11, 2008 at 1:57 PM, Seth Willits <[EMAIL PROTECTED]> wrote:
> If it's what I think you're talking about then: No, nil is used as a marker
> for the variable argument list to say "this is the end of the list." It's
> not actually inserted into the dictionary at all. Why it's required is
On Oct 11, 2008, at 4:51 AM, Stelian Iancu wrote:
Hmm, that's weird. In some official iPhone examples from Apple, they
do exactly that: they put nil as the last element in an array. So
what's up with that?
If it's what I think you're talking about then: No, nil is used as a
marker for th
On Sat, Oct 11, 2008 at 5:51 AM, Andrew Farmer <[EMAIL PROTECTED]> wrote:
> On 10 Oct 08, at 19:28, Ian Joyner wrote:
>>
>> So it's really a workaround for this situation. I think therefore there
>> are several constructs to represent the same concept of "lack of presence" –
>> nil, Nil, Null, and
On 10 Oct 08, at 19:28, Ian Joyner wrote:
So it's really a workaround for this situation. I think therefore
there are several constructs to represent the same concept of "lack
of presence" – nil, Nil, Null, and NSNull.
Fewer than you think, actually. nil, Nil, and NULL are all internally
s
--- On Fri, 10/10/08, Ian Joyner <[EMAIL PROTECTED]> wrote:
> I'll have to think more about this. I'm not sure
> that KVO can't be
> done in a type-safe manner.
I guess KVO can be done in a type safe manner, but not with the interesting way
that objective-c does it. i.e. it can synthesize all
On 11/10/2008, at 2:18 PM, Kyle Sluder wrote:
On Fri, Oct 10, 2008 at 10:33 PM, Ian Joyner <[EMAIL PROTECTED]> wrote:
So we must be dependent on testing, which I find compelling like
agile
programming, but ultimately very hit and miss.
Luckily the Developer Tools come with the OCUnit unit t
On Fri, Oct 10, 2008 at 10:33 PM, Ian Joyner <[EMAIL PROTECTED]> wrote:
> So we must be dependent on testing, which I find compelling like agile
> programming, but ultimately very hit and miss.
Luckily the Developer Tools come with the OCUnit unit testing framework.
>> If it's a strong type syste
On 11/10/2008, at 12:31 PM, Kyle Sluder wrote:
On Fri, Oct 10, 2008 at 8:40 PM, Ian Joyner <[EMAIL PROTECTED]> wrote:
I'm just trying to work out what NSNull really is in the Cocoa
context. Is
it an object in Cocoa? I think (from other environments) that it is
a type
signifying "no object".
On 11/10/2008, at 11:58 AM, Seth Willits wrote:
On Oct 10, 2008, at 5:40 PM, Ian Joyner wrote:
I'm just trying to work out what NSNull really is in the Cocoa
context. Is it an object in Cocoa?
As I said, yes. It's truly an object. (A singleton, as well.)
Since NSNull may be a "valid" va
On Fri, Oct 10, 2008 at 8:40 PM, Ian Joyner <[EMAIL PROTECTED]> wrote:
> I'm just trying to work out what NSNull really is in the Cocoa context. Is
> it an object in Cocoa? I think (from other environments) that it is a type
> signifying "no object". Since NSNull may be a "valid" value of any other
On Oct 10, 2008, at 5:40 PM, Ian Joyner wrote:
I'm just trying to work out what NSNull really is in the Cocoa
context. Is it an object in Cocoa?
As I said, yes. It's truly an object. (A singleton, as well.)
Since NSNull may be a "valid" value of any other type, is it counted
as a subtyp
On 11/10/2008, at 9:33 AM, Seth Willits wrote:
On Oct 10, 2008, at 3:20 PM, DKJ wrote:
I've made an NSDictionary where the values are strings. Is there a
difference between setting a value as [NSNull null] and setting it
as @""? (I've been using the former.)
Is there a difference? Definit
On Fri, Oct 10, 2008 at 5:11 PM, Colin Barrett <[EMAIL PROTECTED]> wrote:
> It is up to the caller of objectForKey:
> (which returns id) to check the type of the returned object and make
> sure it is what you are expecting it to be.
To go further... it isn't important what the type is are run tim
On Fri, Oct 10, 2008 at 3:20 PM, DKJ <[EMAIL PROTECTED]> wrote:
> I've made an NSDictionary where the values are strings. Is there a
> difference between setting a value as [NSNull null] and setting it as @""?
> (I've been using the former.)
It's up to you. Unlike other languages, Cocoa dictionari
On Oct 10, 2008, at 3:20 PM, DKJ wrote:
I've made an NSDictionary where the values are strings. Is there a
difference between setting a value as [NSNull null] and setting it
as @""? (I've been using the former.)
Is there a difference? Definitely. One is an instance of NSString, the
other
I've made an NSDictionary where the values are strings. Is there a
difference between setting a value as [NSNull null] and setting it as
@""? (I've been using the former.)
dkj
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not po
28 matches
Mail list logo
