• 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
Compile errors aren't so good
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Compile errors aren't so good


  • Subject: Compile errors aren't so good
  • From: "Theodore H. Smith" <email@hidden>
  • Date: Fri, 20 May 2005 20:37:12 +0100

I have some C++ class functions declared, which are not coded.

It seems that I can build my app, calling these functions, even though these functions have not been written! Can I make Xcode catch this??? I'd expect it to, and CodeWarrior does it.

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.


MacMFCShims.mm:75: choosing `typename _Alloc::reference std::basic_string<_CharT, _Traits, _Alloc>::operator[](typename _Alloc::size_type) [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]' over `operator[]'


This doesn't sound good to me... Is it saying that it's choosing something complicated over something simple? The code is this:

	if (s[0] != '/') { // s is a C++ "string" class.

If it is doing what it's supposed to, how can I stop making it tell me all about it, and just silently get on with the job?


MacMFCShims.h:153: control reaches end of non-void function
This was actually marked as a "soft error", IE it didn't stop building. This is totally wrong, it's a proper error that should make code unbuildable.




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.



There are loads of other errors I've gotten that are actually the compiler not doing what I want it to, but I think I can fix that myself.



-- elfdata.com/plugin/ Industrial strength string processing, made easy.

"All things are logical. Putting free-will in the slot for premises in
a logical system, makes all of life both understandable, and free."

_______________________________________________
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: Compile errors aren't so good
      • From: Jerry <email@hidden>
    • Re: Compile errors aren't so good
      • From: Frederick Cheung <email@hidden>
  • Prev by Date: Permissions
  • Next by Date: Re: Compile errors aren't so good
  • Previous by thread: Re: Permissions
  • Next by thread: Re: Compile errors aren't so good
  • Index(es):
    • Date
    • Thread