C++ has nothing to do with my previous statement. C++ is object oriented. It's plagued with similar problems than Java in terms of performance.
I was talking about writing the machine code by hand, not relying on a compiler's optimizer to do so. C is a bit better than C++ but if you use a cross platform compiler (like GNU) and you end up on a platform for which not all the optimizations have been tweaked into the compiler you are lost... If you write in C and are concerned by performance, you should at least look at the machine code generated by the compiler to make sure that it does the job correctly. Writing machine code directly, you can tune your code for your specific needs taking into account the available hardware optimizations even on RISC type architectures, you need to read the hardware specs.... Of course this alternative is non-portable but it will be faster than Java or C# Luc On Wed, 2009-08-12 at 06:34 +0700, Daniel wrote: > On Wed, Aug 12, 2009 at 6:02 AM, Luc > Prefontaine<lprefonta...@softaddicts.ca> wrote: > > > > If your algorithm is single threaded and performance is a must then even > > Java should be tossed away. > > Any native machine code equivalent would be faster than Java... > > Pay attention when making assumptions: > http://stackoverflow.com/questions/145110/c-performance-vs-java-c > > (I agree with the rest of what you said, though) > > Cheers, > Daniel > > > > Luc Préfontaine Armageddon was yesterday, today we have a real problem... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
