They are going to open little bit the API so all the game code can be done with C++.
Sounds good.
Hmm… what effect will this have on the rest of us who use Javascript (or C#) and will not be creating games for the iPhone?
thats a pretty cool idea!
none as mono is and remains the core for all platforms 
(on the iphone, to my understanding, there is just the option to get rid of it for the built game)
As I commented on the blog, I hope rather than they let you keep coding in UnityScript/C# and convert it to C++ code automatically behind the scenes… C++ IS still more difficult to program in especially for people new to all this.
Especially when someone tries “tricks” like that inside a well-designed gameengine:
void* myMemory;
myMemory = malloc(34 * typeof(int));
But yeah, a very cool feature indeed.
conversion behind the scene wouldn’t help. would be as illegal by 3.3.1 as going with C# / JS directly.
Splendid.
Splendid, this is excellent news.
C++ really isn’t all that scary and is my preferred language anyway. If you’re worried about memory management then you can always use templates and smart pointers in there instead for allocation which destruct based on scope or usage (and of which there are plenty of free examples out on the web), however it’s just about defensive coding practices. C++ also has many excellent debugging and diagnostic tools, as well as a huge plethora of libraries (just make sure they’re available for all platforms you intend to target), and cross platform development is quite feasible with it, though you do need wrappers around certain things, which I hope the UT SDK will cover.
I learnt to program so that I could use Unity. I chose Javascript because of all the excellent JS tutorials around the Unity scene.
Learning a new language is a lot less daunting than learning to program.
It does seem as if would have some potential benefits, but it would also be a lot of work for UT and the majority of users. I’m glad there is a plan B, and I don’t fear it, but I hope things are able to continue where the existing languages continue to be an option for iPhone development.
Perhaps not for some, but for others, like me, it’s Unity’s easy scripting language that tipped the balance in my decision to use Unity over other engines.
I read David’s blog post and, to be honest, I still am not sure what exactly he’s saying. If we will no longer be able to script in JavaScript in Unity, or if we loose functionality because we choose to script in Javascript, then that’ll reflect a huge change in Unity’s future.
Although I think David’s wording is a bit ambiguous (and that could just be the way I am reading it) I’m hoping that I’m completely off the mark on this.
To my understanding, they add this additional level for the iphone to be able to walk without mono, but it did not sound like mono is gone.
on all other platforms its just another .NET language and I doubt that people, unlike they just want to copy over code from the iphone, are going to use it there as all will go through the .NET compiler and I doubt that all C++ features will be covered on that go
They commented in the blog that this option still doesn’t solve the ToS issue…it has to be “original” code to not violate it.
wait, so you’ll be able to write scripts in c++, just like we do with c# and javascript? :o
Is it just for iPhone or for normal games too?
as you see in the blog for both.
difference is just that outside the iphone, the C++ code will be pushed through a self done C++ to .NET compiler and become an assembly (the same that happens on the iphone for the editor side so you can still use it for the editor to hook stuff up. without that, unity would be totally pointless to be used if the editor aspect is gone. if thats the target of someone then choosing unity would be the totally wrong decision right from minute 1 ^^)
So when David H. said this:
Was he referring to just the existing iPhone code or all the code examples in the docs and Wiki will no longer be functional.
Looks like I’m the lone soul concerned about this though, guess everyone here is a C++ coder. :roll:
He’s talking about examples, snippets and extensions…so, tutorials, example projects, wiki entries and scripts and extensions that other developers have made. As of now, they’re all in C#/UnityScript/Boo.
It would also mean that any iPhone code currently written, would have to be re-written.
Multi inheritance how I missed thee
Why not Objective-C?