Given the number of performance-related discussions in this maillist of 
late, I thought I'd forward this article:
http://www-106.ibm.com/developerworks/java/library/j-jtp04223.html

It's about Java, but I think it's still worthwhile reading for Ocaml 
programmers.  The lesson to learn here is that performance is tricky- what 
you think will obviously be a problem often isn't, and what you think 
won't be a problem can be.  Make it work correctly first, then measure 
performance, then enhance for performance if necessary.

Another comment that applies to both languages is that if it's a glaringly 
obvious problem, the compiler people are probably already working on it 
(or possibly already solved it).

Brian


-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners