Re: Tracking down type mismatches
Re: Tracking down type mismatches
- Subject: Re: Tracking down type mismatches
- From: Bryan Pietrzak <email@hidden>
- Date: Wed, 6 Jul 2005 15:59:21 -0500
On Jul 6, 2005, at 4:17 PM, Tim Conkling wrote:
I just changed the type of a member variable of a class from 'short'
to 'long'. This will have a big effect on the way my program works,
and I can't seem to get Xcode (2.1) to help me track down all the
places where I am using shorts that should be changed to longs.
For example, there is a member function in this object called
getRows(). It used to return a short and now it returns a long. There
are many places in my code where I'm doing something like:
short rows = level->getRows();
I would like to see a warning saying that I'm implicitly casting from
a long to a short so that I can correct all instances of this sort of
thing.
I've been through all of settings in the "Warnings" section of my
Build Configuration, and I couldn't find anything that does what I
want. I added -Wall to the "Other Warning Flags" build configuration
with no luck.
What am I doing wrong? Why am I not seeing warnings about this sort of
thing? I have cleaned and recompiled my program several times to no
avail.
This might sound dumb, but what about changing the function
(temporarily) to return void? Then compile and wherever there are
errors you can check that the code is working with a long not a short.
Skanky I know, but may be effective :)
Bryan
_______________________________________________
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