I'm not sure but considering that quite a few .lua files are inside the angry bird app folder, I'd say they used LUA at some aspects.
But from what I've heard, LUA isn't a primary language, just something to script with.
That said, I'm not a obj-c programmer either, so take my word with a grain of salt.
As the two languages are both based on the C syntax there's a lot of cross compatibility between the basic parts of your code however the interactions with the phone are both done through the respective sdk's so you're gonna have to make changes to account for that. Also worth bearing in mind is that objective c on the iphone isn't garbage collected so you'll need to worry about memory management!
核心至少必须是C。如果我是他们，我会用 C 编写核心，并在 Android 上封装 java（我认为你可以做到这一点），而在 iPhone 上用 Objective C 编写（我知道你可以做到）。
Has to be C for the core at least. If I was them I would write the core in C and wrap java around it for android (I think you can do that) and objective c for the iPhone (I know you can do that).
I always assumed that these developers program core functionality in c/c++ and then use native development kits to link the two. For example I know in android development you can use the NDK to wrap java around c/c++
发布评论
评论（5）
我不确定，但考虑到愤怒的小鸟应用程序文件夹中有相当多的 .lua 文件，我想说他们在某些方面使用了 LUA。
但据我所知，LUA 并不是主要语言，只是用于编写脚本的语言。
也就是说，我也不是 obj-c 程序员，所以请对我的话持保留态度。
跟进链接
https://web.archive.org/web/20120502071633/http://blog.anscamobile.com/2010/04/lua-the-lingua-franca-of-iphone-games/
I'm not sure but considering that quite a few .lua files are inside the angry bird app folder, I'd say they used LUA at some aspects.
But from what I've heard, LUA isn't a primary language, just something to script with.
That said, I'm not a obj-c programmer either, so take my word with a grain of salt.
Follow up link
https://web.archive.org/web/20120502071633/http://blog.anscamobile.com/2010/04/lua-the-lingua-franca-of-iphone-games/
Android 应用程序使用 Android 开发套件使用 Java 进行编码，iPhone 游戏使用 Objective C 进行编码
Android 开发套件可在此处获取
http://developer.android.com/index.html
此处提供 iphone (iOS) 开发套件（注意需要mac）
http://developer.apple.com/devcenter/ios/index.action
由于这两种语言都基于 C 语法，因此代码的基本部分之间存在很多交叉兼容性，但是与手机的交互都是通过各自的 sdk 完成的，因此您必须进行更改才能解决这一问题。另外值得记住的是，iPhone 上的 Objective C 不会进行垃圾收集，因此您需要担心内存管理！
Android apps are coded in Java with the android development kit, iphone games are coded in objective c
Android dev kit is available here
http://developer.android.com/index.html
iphone (iOS) development kit available here (Caution requires a mac)
http://developer.apple.com/devcenter/ios/index.action
As the two languages are both based on the C syntax there's a lot of cross compatibility between the basic parts of your code however the interactions with the phone are both done through the respective sdk's so you're gonna have to make changes to account for that. Also worth bearing in mind is that objective c on the iphone isn't garbage collected so you'll need to worry about memory management!
AngryBirds（以及其他一些游戏）使用 C/++ 代码和 NDK。来源：使用什么语言对“愤怒的小鸟”进行编程'应用程序？，http://www.gamasutra.com/查看/feature/6481/postmortem_vector_units_riptide_.php
AngryBirds (and some other games) are using C/++ code and the NDK. Sources: What language was used to program the 'Angry Birds' app?, http://www.gamasutra.com/view/feature/6481/postmortem_vector_units_riptide_.php
核心至少必须是C。如果我是他们，我会用 C 编写核心，并在 Android 上封装 java（我认为你可以做到这一点），而在 iPhone 上用 Objective C 编写（我知道你可以做到）。
Has to be C for the core at least. If I was them I would write the core in C and wrap java around it for android (I think you can do that) and objective c for the iPhone (I know you can do that).
我一直假设这些开发人员使用 c/c++ 编写核心功能，然后使用本机开发套件将两者链接起来。例如，我知道在 android 开发中，您可以使用 NDK 将 java 包装在 c/c++
http: //developer.android.com/sdk/ndk/index.html
讽刺的是，在这种情况下，Java 并不是“构建一次，到处运行”的语言 :p
I always assumed that these developers program core functionality in c/c++ and then use native development kits to link the two. For example I know in android development you can use the NDK to wrap java around c/c++
http://developer.android.com/sdk/ndk/index.html
Ironically Java isn't the "build once, run every everywhere" language in this case :p