>I'm curious, how are you going to be able to establish the productivity
>gain/loss once your game is finished?

It's certainly not going to be scientific, that's for sure.  :)  I just 
figure I'll have a better idea of how caml handles a complete project (or 
at least how I handle a complete project with caml) once I'm done.  It'll 
be more of a personal metric of productivity, but since I work by myself, 
that's fine for me.

 > Are you using O'Caml for all of your code in the game? Are you using 
external
>libraries extensively?

The only external library is gl/d3d, at least I hope to keep it that way 
(well, I'll have to interface to dsound as well, obviously).

>I happened to look at d6.com web site.

This game isn't up there, it's still a long ways from being finished, sadly.

To have some actual potentially list-worthy content in this mail:  I have 
found caml code easier to refactor than C.  Moving blocks of code around is 
pretty easy because of local functions/closures.

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