Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
by rimantas on Thursday April 08, 2010 @05:33PM
(#1251059)
Yeah, as if Flash is known for its stability (especially on the Apple platform) and security…
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
by tumult on Thursday April 08, 2010 @06:42PM
(#1251253)
This affects anything that isn't C, C++, or Objective-C. Pay attention.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
by rimantas on Thursday April 08, 2010 @07:07PM
(#1251339)
Yes it does. My comment was about Flash however.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
by catch23 on Friday April 09, 2010 @01:10PM
(#1253214)
you're preaching to the choir already. I'm pretty sure we're all in agreement on how sucky the Flash runtime is already.
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
by towndrunk on Thursday April 08, 2010 @06:24PM
(#1251207)
You haven't used XCode's Build and Analyze have you?
Re:New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
by cdonnellytx on Thursday April 08, 2010 @06:51PM
(#1251286)
I have, and it has some significant bugs that make it difficult to use:
- There is a bug with the compiler not properly counting references when assigning a variable that needs a release to a property marked "retain". The property will increment the reference count, expecting the caller to decrement it, but the static analyzer does not see this, and so fails to warn.
- http://www.openradar.appspot.com/7338181 - CodeSense fails to work when Static Analysis is turned on.
(DISCLAIMER: I am using Xcode 3.2.1 on Snow Leopard 10.6.3)
2. ???
3. Therefore, if you write native iPhone apps, you must use C derivatives that expose raw pointers and direct memory access.