Re: Possible bug in NSCalendarDate
Re: Possible bug in NSCalendarDate
- Subject: Re: Possible bug in NSCalendarDate
- From: Shawn Erickson <email@hidden>
- Date: Wed, 11 Feb 2004 14:38:06 -0800
On Feb 11, 2004, at 2:27 PM, Jeremy Dronfield wrote:
On 11 Feb 2004, at 7:08 pm, Shawn Erickson wrote:
Something else must be going wrong (or some funky compiler/optimizer
bug which very unlikely)...
What you are doing in the second implementation is identical to the
first from the point of view of the initWithString:calendarFormat:
message.
When you get a nil back what does pathDate point at? Is it nil? If
not does the string look like what you expect?
I think I must have hit a rare bug in the compiler or the debugger.
Restarting XCode and running another test (without altering my code),
I find I'm unable to reproduce the problem. Damn. I wasted about an
hour trying to work out what was going wrong, and it turns out to be
someone else's fault. I think the compiler is the most likely culprit,
because I was getting a nil string error printing to the console
before I tried debugging. I'm not sure about submitting a bug report,
since I can't reproduce the bug.
Actually it is likely from a defect in your code at some point time
that may have persisted because not all of your code was rebuilt
because of a slip up in Xcode's predictive or normal compilation checks
(it attempts to only rebuild what is needed). This can be aggravated by
zero link. If you hit strange bugs like this first try doing a clean
build of things... or you have a defect of some type that is not easy
to trigger consistently.
It is very unlikely that it was caused by an issue with the compiler
itself (as in the code it generates).
- Shawn
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.