Obj-C borrows SmallTalk's message passing, and represents a fundamentally different way of extending C than the developments that influenced Processing. There are some similarities, but the syntax is very different.

Having said that, you can probably implement the algorithm you saw in Processing. You may have to translate some Obj-C idiom to do it, so it could look a little different, but its certainly possible.

I should have addressed this in my earlier post but I also wanted to say that I'm not sure why a compiler that results in native machine code would be an improvement. If you're looking for speed improvements, the truth is that a modern JVM  (one that uses JIT) is pretty quick. The GNU compiler for Java (part of gcc) supports compiling Java into native machine code, and while there's a small decrease in startup times it takes heavy optimizations, both from the compiler and from the coder, to get the native code to run faster than the Java code.

It probably wouldn't be terribly difficult to implement a version of Processing that compiles down to native code, but I think it would only be an improvement for really advanced programmers. If your concern is speed there are probably many idioms and optimizations you can make before the JVM's performance is your bottleneck.

Thanks lonnen, your input is really interetesting. I saw the code, and I always wanted to create an app for the ipad,itouch and iphone but they use objective C. However, I believe with the advent of HTML5 and the canvas, it will be pretty soon when we can have processingjs scripts running on it.

I was comparing the two types of syntax as it relate towards how difficult it would be to learn, however, my first love is processing.

PROCESSING ROCKS!!!

However, I believe with the advent of HTML5 and the canvas, it will be pretty soon when we can have processingjs scripts running on it.

Actually, with Processing.js, they already run on these platforms. I think somebody even added specific features (like multitouch). Just search the old forum.