On Oct 11, 2009, at 5:20 PM, Clark Cox wrote: On Fri, Oct 9, 2009 at 12:58 PM, McLaughlin, Michael P. < email@hidden> wrote: The recent thread on Xcode bugs reminded that I forgot to post this one
although I no longer have an example right in front of me.
I have had the experience, two or three times, of creating a new Cocoa class
(and header) then trying to edit the contents to construct a new category of
an existing class. Every time, I got an "Internal error" from Xcode and had
to abort and start over.
What is the actual error? Was there a stack trace printed to the console? What version of Xcode are you using? etc. I now make Category files in BBEdit first, then
import them.
Has anyone else seen anything like this?
Have you filed a bug yet?
This bug has been filed, at least twice. (With stack traces.) Here is a message that I received after I filed a report on it:
>This is a follow up to Bug ID# 6630772. After further investigation it has been determined that this is a known issue, which is >currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 6418302. The >original bug number being used to track this duplicate issue can be found in the State column, in this format: Duplicate/OrigBug#.
>Thank you for submitting this bug report. We truly appreciate your assistance in helping us discover and isolate bugs.
Here is a workaround: When you want a line like @interface ClassName(CategoryName) you type it in reverse: start by typing a fragment like (categoryName) then insert the "ClassName" in front, and then insert "@interface ";
By the way, I have belatedly noticed the date when this reply was allegedly sent to me: March 4, 1909 2:13:03 PM EST That is impressively prompt. Or may it is a Y2K problem that has been hiding since System 9 was the current Mac OS.
Christopher Henrich mathinteract.com
|