• 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: gcc 4.2 generates error that was OK before
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gcc 4.2 generates error that was OK before


  • Subject: Re: gcc 4.2 generates error that was OK before
  • From: Rippit the Ogg Frog <email@hidden>
  • Date: Tue, 22 Sep 2009 22:56:44 -0700

Alastair Houghton wrote:
I ask because the C++ language syntax has all kinds of problems thanks to the thoughtless way its grammar was extended (no, I do not worship Stroustrup, unlike---apparently---half the developer community).

C++ is my favorite language for what I feel are good reasons, but it took me a long, long time to master it.


It's a fiendishly complex language, and so it's very hard to implement it correctly in a compiler.

Loosely speaking, C++ has a complex language but simple libraries. Some other languages like Java have a simple language but complex libraries. The compilers tend to be more correct but I imagine the libraries tend to be buggier.

An example of the difficulty of getting the compiler right is that I was once able to get CodeWarrior to instantiate an object of abstract base class type. The pure virtual member functions all had a nil pointers in the vtable and so would cause crashes when I tried to call them.

I asked about this on the C++ newsgroup, and there was much debate as to whether I was wrong or CodeWarrior was. It was definitely an edge case as far as the standard was concerned. In the end it was concluded that my source was incorrect - but when I pointed out that CodeWarrior should have refused to compile that line of code, my contact at Metrowerks agreed and logged a bug against it.

I don't recall now exactly what I did but I expect I could dig it up if someone were curious. I was actually trying to do something completely different than what resulted.

All this is meant to say, you're doing pretty good if this is the only C++ compiler bug you have to deal with.

--
Rippit the Ogg Frog
email@hidden
http://www.oggfrog.com/
_______________________________________________
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: gcc 4.2 generates error that was OK before
      • From: Mark Wagner <email@hidden>
References: 
 >gcc 4.2 generates error that was OK before (From: Steve Mills <email@hidden>)
 >Re: gcc 4.2 generates error that was OK before (From: Alastair Houghton <email@hidden>)

  • Prev by Date: Xcode3.2-IB: No outlet/action section in inspector panel (identity)
  • Next by Date: Finding unused images in Project
  • Previous by thread: Re: gcc 4.2 generates error that was OK before
  • Next by thread: Re: gcc 4.2 generates error that was OK before
  • Index(es):
    • Date
    • Thread