• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode 2 Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 2 Question


  • Subject: Re: Xcode 2 Question
  • From: Markian Hlynka <email@hidden>
  • Date: Thu, 5 May 2005 16:35:01 -0600


On May 4, 2005, at 17:03, Shawn Erickson wrote:


On May 4, 2005, at 3:36 PM, Markian Hlynka wrote:

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;

Ugh ;-)

If you really want to insure a certain sizing consider using int16_t (#include <stdint.h>) instead of short (is a signed short really what you want?).


I'm aware of stdint.h, though I was also aware that it wasn't officially C++ yet. But, is there something wrong with just using "short"? I didn't need precisely 16 bits... I just didn't need anywhere near 32 of 'em. ie, I wanted something smaller, but not too small. char or byte would probably have done as well.


Should I be explicitly choosing my sizes, then? Is it bad form to use "short" nowadays?

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.

Under Xcode 2.0 I see only "typedef PartialMove" listed in the popup and functions before and after list just fine.
Actually after toggling out of xcode and back to the window the popup now shows the following (at fist it didn't list the operators)...

yeah, but it doesn't show the _name of the typedef. In my case, though, it's much weirder. Here's a link:
http://www.cs.ualberta.ca/~markian/xcodefuncmenu.jpg


So, right at the bottom you can see the mark for Move_T. If you look at the popup, you'll see Move_T under the highlight. If I select Move_T, it highlights Move_T on line 202. If I select operator== or != from the popup UNDER Move_T, then it selects the operators in PartialMove ABOVE the #pragma mark Move_T. Note also that they're in REVERSE order in the popup! Selecting the typedef after Move_T inexplicable selects an index in a for loop on line 271! the last 'i' in this statement:
this->captures[i] = src.captures[i];
Does that make ans sense?! And selecting the typedef immediately ABOVE Move_T in the popup selects the 'c' on line 187. I'm willing to believe that they're out of order because maybe Xcode is trying to sort them alphabetically. However, if that was the case, why is asking to go to a typedef selecting variables?!




On a related note... is there anyway to search the reported bug database? I mean, to see bugs other than the ones _I_ originated?

No. Apple considers submitted reports private between the submitter and Apple.


I have seen some talk about Apple considering to allow the submitter to allow it be public (at least what the submitter provides to be public) with a selection at the time of submit . However who knows if that was any more then speculation, etc. that lawyer may shoot down.

I don't understand this policy, other than in the case of a big company like Apple, I guess there's a target.. you know who to sue. But, open-source projects have public databases. This is useful, because even if you don't plan on fixing a bug, you can determine if someone else has had the same issue or not!


Markian

_______________________________________________
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


  • Follow-Ups:
    • Re: Xcode 2 Question
      • From: Clark Cox <email@hidden>
References: 
 >Xcode 2 Question (From: Markian Hlynka <email@hidden>)
 >Re: Xcode 2 Question (From: Shawn Erickson <email@hidden>)

  • Prev by Date: Re: Xcode 2 Question
  • Next by Date: precompiled header & distcc
  • Previous by thread: Re: Xcode 2 Question
  • Next by thread: Re: Xcode 2 Question
  • Index(es):
    • Date
    • Thread