• 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: Xcode 5.1.1 and Xcode 3.2.6 on OS X 10.9.4
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 5.1.1 and Xcode 3.2.6 on OS X 10.9.4


  • Subject: Re: Xcode 5.1.1 and Xcode 3.2.6 on OS X 10.9.4
  • From: "Clark S. Cox III" <email@hidden>
  • Date: Sat, 09 Aug 2014 09:39:26 -0700


On Aug 9, 2014, at 03:42, email@hidden wrote:

Hi,

I first started out on OS X 10.9.4 with Xcode 3.2.6.

That was your first mistake :)
Xcode 3.2.6 was designed to run on OS X 10.6 and *only* OS X 10.6. Any strange behavior you see is par for the course when running in an unsupported, untested configuration..



Since I installed Xcode 5.1.1 alongside to it, I am experiencing weird
problems. Like this piece of test code

pxmempooltest1* mypxmempooltest1[dpxg1_test_mempool_count];

pxfor(i,dpxg1_test_mempool_count){
mypxmempooltest1[i]=new(pxmempooltest1)(i);
pxoka(mypxmempooltest1[i]->itsmempooltest1data==(123+i))
}


It simply allocates a fairly large number of instances of a simple class (on the heap). After some forty-thousand loops
no memory is allocated. This test code has worked ok for many years...

Is it ok to have these two versions of Xcode on the same machine?

No. It is not OK to have Xcode 3.2 on anything later than OS X 10.6 in the first place, regardless of whether or not you have Xcode 5.x installed. I would recommend, if you absolutely need to run Xcode 3, that you use a virtual machine running 10.6.


-- 
Clark Smith Cox III
email@hidden

 _______________________________________________
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

  • Prev by Date: Re: Resolving link errors from using two static libs that contain the same symbols
  • Next by Date: Bindings in Swift
  • Previous by thread: Re: Resolving link errors from using two static libs that contain the same symbols
  • Next by thread: Bindings in Swift
  • Index(es):
    • Date
    • Thread