• 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: Why XCode and not Code Warrior
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why XCode and not Code Warrior


  • Subject: Re: Why XCode and not Code Warrior
  • From: "Sean McBride" <email@hidden>
  • Date: Thu, 11 Aug 2005 09:44:31 -0400
  • Organization: Rogue Research

On 2005-08-11 12:43, Finlay Dobbie said:

>CodeWarrior is dead.

No, CodeWarrior is dying, present tense. :)

>Support will end at the end of this year, there
>will (may?) be one more release and that's it.

They say there will be one more release this fall, and support will last
for one year from the date of it's release.

>You will not be able to
>use CodeWarrior to compile Intel binaries, restricting your
>applications to be run only in the Rosetta compatibility environment
>on future Macintosh with Intel processor machines:

True.  Unless someone makes a gcc plugin; I believe they said there is
just such an example that will come with CW 10, but its not fully baked.

--
____________________________________________________________
Sean McBride, B. Eng                 email@hidden
Rogue Research                        www.rogue-research.com
Mac Software Developer              Montréal, Québec, Canada


 _______________________________________________
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

References: 
 >Why XCode and not Code Warrior (From: "Alyssa Meier" <email@hidden>)
 >Re: Why XCode and not Code Warrior (From: Finlay Dobbie <email@hidden>)

  • Prev by Date: Re: Why XCode and not Code Warrior
  • Next by Date: Adding JUnit unit-tests to an XCode project
  • Previous by thread: Re: Why XCode and not Code Warrior
  • Next by thread: Re: Why XCode and not Code Warrior
  • Index(es):
    • Date
    • Thread