>how important is operator overloading?

I'm amazed that people who are interested in high level languages are 
asking these questions (not to attack you personally, just the overall 
attitude)!

I replied to most of this issue in my previous post, but come on people, 
the job of a language is to make the programmer's life easier.  Software 
quality is horrible, for the most part, and we don't even get this horrible 
software on time.  Why?  Hint:  it's not because correct programs are 
running too slow and developers are spending that time optimizing.  It's 
because complex software is hard to write correctly.  The language should 
help with this.  Ocaml helps in a lot of ways with this problem, but when 
writing numerical code it doesn't help very much, or as much as it 
could.  That is what I'm complaining about.

If I could write matlab-style syntax in ocaml, hundreds of lines of code in 
my game would just disappear.  That would be wonderful!  It would mean it 
was easier and faster to write, to debug, and that when I realize I didn't 
actually want to do a certain operation, I could change it quickly.  When I 
finally figure out what I want to do and how I want to do it, I'll optimize it.

And besides, the entire idea behind a garbage collector is that it's fast 
at handling tons of small allocations!  I use tons of matrix -> matrix -> 
matrix operations (like add, mult, etc. in and attempt to make more 
readable code) and the performance is perfectly acceptable for 
development.  I will optimize things later, but LATER, and only if I need to.

Frustrated,
Chris


-------------------
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