From: "Warp" <warplayer@free.fr>
To: "John Max Skaller" <skaller@ozemail.com.au>
Cc: <caml-list@inria.fr>, "Luc Mazardo" <Luc.Mazardo@cvf.fr>
Subject: Re: [Caml-list] OCamlSDL
Date: Fri, 19 Apr 2002 17:58:49 +0200 [thread overview]
Message-ID: <006101c1e7bb$18ebc610$3900a8c0@warp> (raw)
In-Reply-To: <3CC03C7D.8020505@ozemail.com.au>
> >I'm currently working at using OCaml as a script top-level for Direct3D.
For
> >now it works just fine, and this summer our team will work on a big game
> >project almost entirely written in OCaml. Altough "game" things are
perhaps
> >not the kind of projects for which OCaml was actually designed, I think
we
> >can get some big payoff by using such a nice langage.
> >
> No. Yes.:-)
>
> Games are the ultimate application.
> You need a very good language to write a decent game
> and have it work. Ocaml is a superb choice.
> It is well suited to it. Have a look at the complete
> and utter rubbish the commercial sector generally offers:
> most of them can't even get basic game logic right.
>
> Oh yes, they have superb graphics ... elaborate scenarios ..
>
> Please. Write a decent game. There isn't one.
I think also that Ocaml is a good choice. When you're looking what's
happening in the industry, most of the companies are relying on home-made
script langages, with few features and lots of bugs. Some game scripting
langage have evolved and are now available for OpenSource, but most of the
time the design choice is to be "easier" than C ( no types ! ), which of
course reduce the potential range of application of such a langage.
That's why ocaml is good : you only need to have a slim C/C++ library to
work with and then you can code ALL your game - including tools - in OCaml.
Nicolas Cannasse
-------------------
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
next prev parent reply other threads:[~2002-04-19 15:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 14:32 Luc Mazardo
2002-04-18 22:03 ` Warp
2002-04-19 15:49 ` John Max Skaller
2002-04-19 15:58 ` Warp [this message]
2002-04-19 16:06 ` Will Benton
2002-04-19 16:13 ` Stefano Lanzavecchia
2002-04-19 16:27 ` Will Benton
2002-04-19 17:20 ` Warp
2002-04-20 9:06 ` John Max Skaller
2002-04-20 12:22 ` Tim Freeman
2002-04-20 12:51 ` Sven
2002-04-22 6:55 ` Tom
2002-04-22 20:05 ` John Max Skaller
2002-04-21 22:56 ` John Max Skaller
2002-04-22 6:53 ` William Chesters
2002-04-23 14:50 ` Oliver Bandel
2002-04-23 15:12 ` Stefano Lanzavecchia
2002-04-24 1:00 ` Jacques Garrigue
2002-04-24 1:07 ` John Max Skaller
2002-04-24 7:02 ` Sven
2002-04-24 9:04 ` John Max Skaller
2002-04-24 9:31 ` Sven
2002-04-24 9:42 ` Jérôme Marant
2002-04-24 11:00 ` Jérôme Marant
2002-04-29 10:11 ` Sven
2002-04-24 16:56 ` Oliver Bandel
2002-04-19 17:16 ` Warp
2002-04-19 17:45 ` Sven
2002-04-19 18:01 ` Warp
2002-04-19 18:55 ` Vincent Foley
2002-04-20 6:33 ` Alan Schmitt
2002-04-20 12:16 ` Sven
2002-04-20 9:19 ` John Max Skaller
2002-04-20 12:19 ` Sven
2002-04-20 14:47 ` Vitaly Lugovsky
2002-04-20 9:01 ` John Max Skaller
2002-04-21 12:13 ` Oliver Bandel
2002-04-21 12:27 ` Oliver Bandel
2002-04-24 14:02 Damien Doligez
2002-04-24 14:37 ` Christophe Raffalli
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='006101c1e7bb$18ebc610$3900a8c0@warp' \
--to=warplayer@free.fr \
--cc=Luc.Mazardo@cvf.fr \
--cc=caml-list@inria.fr \
--cc=skaller@ozemail.com.au \
/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