> inefficient. The JVM incurs such a commitment to memory indirection that you > can't run it at any sensible speed without resorting to something as > complicated as the hotspot technology. > > BitC isn't going to hit the levels of C, because there is inherent overhead > from type safety. Just for one example, consider array bounds checking. > We're doing various things to mitigate that overhead. Some of that will > work, some of it won't.
yeah, i don't know that anybody has wide & deep numbers & analysis, but things like ocaml and ats purport to do pretty well. _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
