Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Any reason to avoid GCC-4.2 for Leopard and later targeted code?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Any reason to avoid GCC-4.2 for Leopard and later targeted code?

Subject: Re: Any reason to avoid GCC-4.2 for Leopard and later targeted code?
From: Matt Gough <email@hidden>
Date: Fri, 5 Dec 2008 09:29:12 +0100


On 5 Dec 2008, at 05:11, Sean McBride wrote:

GCC-4 is still the "system compiler" on Leopard. For code targetting Leopard and later (linked against the 10.5 SDK) are there any gotchas or other issues I should be aware of before I switch over to using 4.2 to build?
It's working well for me, with one exception: they removed the STL debug feature. So if you use C++, you'll loose the ability to turn on this useful debugging tool.


OK, so dumb question, but :

What is the STL-debug feature?

Sounds like something I wish I had on all along.

Matt
_______________________________________________
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: Any reason to avoid GCC-4.2 for Leopard and later targeted code?
From: "Sean McBride" <email@hidden>


References:  
  >Any reason to avoid GCC-4.2 for Leopard and later targeted code? (From: Jim Correia <email@hidden>)
  >Re: Any reason to avoid GCC-4.2 for Leopard and later targeted code? (From: "Sean McBride" <email@hidden>)




Prev by Date:
Re: Stumped: How to call a function defined in a Framework?

Next by Date:
Re: Any reason to avoid GCC-4.2 for Leopard and later targeted code?

Previous by thread:
Re: Any reason to avoid GCC-4.2 for Leopard and later targeted code?

Next by thread:
Re: Any reason to avoid GCC-4.2 for Leopard and later targeted code?

Index(es):

Date
Thread