caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Michael Vanier <mvanier@cs.caltech.edu>
To: jonathan@meanwhile.freeserve.co.uk
Cc: caml-list@inria.fr
Subject: Re: Games (Re: [Caml-list] Caml productivity.)
Date: Sun, 28 Jul 2002 17:57:42 -0700	[thread overview]
Message-ID: <200207290057.g6T0vgu15557@orchestra.cs.caltech.edu> (raw)
In-Reply-To: <005401c2363d$50206340$890bfea9@mimbi> (jonathan@meanwhile.freeserve.co.uk)


> From: "Jonathan Coupe" <jonathan@meanwhile.freeserve.co.uk>
> Date: Sun, 28 Jul 2002 14:45:50 +0100
> 
> > If you're talking about professional quality games using caml as the main
> > language (as opposed to as a scripting language), it's not really an
> option
> > on this generation of consoles.  Memory in a commercial console game is
> > tightly managed, and caml doesn't give much control over memory management
> > at all.
> 
> Even on a PC, I would have thought that the GC might need some re-writing? I
> haven't seen any suggestion in the docs that it's compatible with realtime
> requirements, ie preventing long periods of garbage collection. That said,
> people ship games with bigger bugs.
> 
> The main thing I've taken from OCaml is using a mixed object/functional
> style with C++ in games. This works well enough so that we'll probably spend
> some money later this year using OpenC++ (an advanced preprocessor developed
> at Xerox) to add closures on top of the C++ compilers we use.
> 
> Finally, although it is a fine language I don't think that OCaml supports
> the right feature mix for game programming. The combination of a more
> sophisticated ObjectiveC language (reflection for modules on top of a C
> style base language, but with Smalltalk debugger and workspace, and C's
> syntactical faults removed), an object library like Unrealscript's and
> reasonable support for FP would seem optimum. I'd insist that it be easier
> to parse than C++, even at the cost of removing a lot of syntactical sugar -
> that way I might actually get a compiler that matches the language spec,
> which still hasn't happened with C++.
> 
> 
> - Jonathan Coupe
> 

Well, why not write that language in ocaml yourself?  Whatever else you can
say about ocaml, it is a superb language for writing other languages in.
Jason Hickey's group here at Caltech use ocaml to write all their compilers
(actually one big compiler with multiple front ends for different
languages).  I know this is a lot of work, but I'm not being totally
tongue-in-cheek here.

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


  reply	other threads:[~2002-07-29 15:49 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-15 21:22 [Caml-list] Caml productivity Pal-Kristian Engstad
2002-07-20 15:16 ` William Chesters
2002-07-22 18:22   ` Pal-Kristian Engstad
2002-07-22 18:41     ` achrist
2002-07-22 19:23       ` Pal-Kristian Engstad
2002-07-22 21:13         ` [Caml-list] CamlIDL and function pointers Michael Tucker
2002-07-23  8:39           ` Xavier Leroy
2002-07-23 13:11             ` Dmitry Bely
2002-07-24 15:00             ` Michael Tucker
2002-07-25  9:36               ` Xavier Leroy
2002-07-22 21:26     ` Games (Re: [Caml-list] Caml productivity.) Oleg
2002-07-23  2:56       ` Issac Trotts
2002-07-23 11:03         ` eijiro_sumii
2002-07-23 16:17           ` Charles Martin
2002-07-29  3:36           ` Andrei de A. Formiga
2002-07-29  6:32             ` Florian Hars
2002-07-29 10:23             ` eijiro_sumii
     [not found]               ` <001901c237a7$9e685920$890bfea9@mimbi>
2002-07-30  4:52                 ` eijiro_sumii
2002-07-30 18:13                   ` Jonathan Coupe
2002-07-30  6:16                     ` eijiro_sumii
2002-08-01 15:39                     ` John Max Skaller
2002-08-01 15:59                       ` Markus Mottl
2002-08-01 16:28                       ` Jonathan Coupe
     [not found]                         ` <86vg6ta9o6.fsf@laurelin.dementia.org>
2002-08-02 12:50                           ` Jonathan Coupe
2002-08-02 14:51                         ` John Max Skaller
2002-07-25  3:19       ` Chris Hecker
2002-07-28 13:45         ` Jonathan Coupe
2002-07-29  0:57           ` Michael Vanier [this message]
2002-07-22 22:00     ` [Caml-list] Caml productivity Alexander V.Voinov
2002-07-20 15:25 ` Oleg
2002-07-22  6:41 ` Tom
2002-07-22 10:46 ` Nicolas Cannasse
2002-07-22 17:46   ` Pal-Kristian Engstad
2002-07-24  3:20     ` Travis Bemann
2002-07-24  9:45       ` Pal-Kristian Engstad
2002-07-26 21:42         ` Chris Hecker
2002-07-27  4:41           ` Issac Trotts
2002-07-27  5:49             ` Chris Hecker
2002-07-27 14:49               ` John Max Skaller
2002-07-27  9:06           ` Oleg
2002-07-27 18:18             ` Chris Hecker
2002-07-29  8:13         ` Nicolas Cannasse
2002-07-30  4:46           ` Travis Bemann
2002-07-24  8:02     ` Nicolas Cannasse
2002-07-24  8:25       ` Jérôme Marant
2002-07-24 10:00       ` Pal-Kristian Engstad
2002-07-27  9:06         ` Oleg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200207290057.g6T0vgu15557@orchestra.cs.caltech.edu \
    --to=mvanier@cs.caltech.edu \
    --cc=caml-list@inria.fr \
    --cc=jonathan@meanwhile.freeserve.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).