Re: Xcode 2 Question
Re: Xcode 2 Question
- Subject: Re: Xcode 2 Question
- From: Clark Cox <email@hidden>
- Date: Wed, 4 May 2005 19:01:28 -0400
On 5/4/05, Markian Hlynka <email@hidden> wrote:
> Hi all.
>
> I don't have tiger yet... (can anyone tell me how to find out when my
> student ADC copy ships?)
>
> Anyway, I have a question about whether something simple is fixed in
> Xcode 2.. If someone has the time to check, I can rejoice in
> anticipation...
>
> In Xcode 1.5, if you had structs with member functions, they completely
> fubared the function menu in xcode. For example:
>
> typedef struct __PartialMove
> {
> //PartialMove is a coordinate!
>
> short r,c; //source and destintion row and column.
> //shorts are 16 bits (2 bytes), at least that's what they are right
> now!
>
> bool operator==(const struct __PartialMove &b)
> {
> return (r == b.r) && (c == b.c);
> }
> bool operator!=(const struct __PartialMove &b)
> {
> return !( (r == b.r) && (c == b.c) );
> //alternatively, (r != b.r) || (c != b.c);
> }
>
> } PartialMove;
>
> The only things that shows up in the function menu in Xcode 1.5 are:
> typedef
> operator!=
> operator==
>
> Worse, nothing following such a struct shows up in the function menu
> either. So, even if I only do it once, my function menu is henceforth
> useless.
>
> BBEdit does a slightly better job with:
> PartialMove
> It would be nice if BBEdit broke up the member functions, but at least
> I can find the definition!
>
> Removing the typedef doesn't help.
But I'd recommend doing it anyway, it's completely redundant in C++.
Additionally, I'd recommend using the class keyword instead, as a
workaround, and because I can't think of any reason not to:
class PartialMove
{
public:
//PartialMove is a coordinate!
short r,c; //source and destintion row and column.
//shorts are 16 bits (2 bytes), at least that's what they are right
now!
bool operator==(const PartialMove &b)
{
return (r == b.r) && (c == b.c);
}
bool operator!=(const PartialMove &b)
{
return !( (r == b.r) && (c == b.c) );
//alternatively, (r != b.r) || (c != b.c);
}
};
> Anyway, if this isn't fixed, I'll file a bug; I can't recall if I ever
> did, or was told that it was a known issue, or what....
It's not fixed, file away.
> On a related note... is there anyway to search the reported bug
> database? I mean, to see bugs other than the ones _I_ originated?
--
Clark S. Cox III
email@hidden
http://www.livejournal.com/users/clarkcox3/
http://homepage.mac.com/clarkcox3/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden