Re: Compile errors aren't so good
Re: Compile errors aren't so good
- Subject: Re: Compile errors aren't so good
- From: Jerry <email@hidden>
- Date: Sat, 21 May 2005 09:15:30 +0100
On 20 May 2005, at 20:37, Theodore H. Smith wrote:
Also, I'm getting annoyed by all these error messages which have no
use to me:
MacMFCShims.mm:75: because worst conversion for the former is
better than worst conversion for the latter
I get this error 3 times from one file on one line, and the code is
actually perfectly good C++.
MyArrays:794: using obsolete binding at `lop'
for(int lop=0; lop<MAXMANDATORY; lop++)
{
I can't see anything wrong there?? I'm getting a tone of these
"obselete bindings", and it's annoying me.
It'll be because you're using "lop" outside the loop, which is an
obsolete C practice. If you want to use "lop" fater the loop has
finished, you need to declare it before the "for" statement;
MyArrays:35: instantiated from here
This isn't even an error. It's just put into my build log window
pane and I have no idea why. It seems like it just feels like
commenting idle remarks about my code, like that something was
instantiated. Seems a bit pointless really.
These are actually useful - you get them when you have an error in
something like inlined or templated code, and it's telling you where
you were trying to use the code in question. In the case of templated
code, this can often give you vital information to work out what's
going wrong (and you need all the help you can get when it comes to
template errors).
Jerry
_______________________________________________
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