caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Chris Hecker <checker@d6.com>
To: Jonathan Coupe <jonathan@meanwhile.freeserve.co.uk>,
	"Joseph R. Kiniry" <kiniry@acm.org>,
	caml-list@inria.fr
Subject: Re: JIT-compilation for OCaml?
Date: Sat, 06 Jan 2001 16:16:04 -0800	[thread overview]
Message-ID: <4.3.2.7.2.20010106160502.00bb4390@shell16.ba.best.com> (raw)
In-Reply-To: <004501c0769e$58e09f00$1cce883e@baby>


> The use of game scripting
>languages with very similar characteristics toOCaml is well accepted
>however - search +GOOL +"Crash Bandicoot" for an example. Typically game
>companies write their own scripting languages. Using a well-supported and
>tested open source language may well be an idea whose time has come.

A couple points:  Several games have used Lua as a scripting language, so developers are already using open source scripting languages.  And, while game developers are relatively flexible on which scripting languages are used, trying to use something that's not C or C++ as the main core programming language would be heresy right now in the game industry (even Java would be considered very risky).  I didn't get the impression that the previous poster was evaluating scripting languages as much as the core language for the project.

For what it's worth, I'm doing a talk about wacky languages at the GDC this year:

http://cmp.bluedot.com/re/attendee/sessionViewer/gdcEventViewer.esp?presentationIds=36554534&searchResults=true&lastChoice=search

And, James Hague (who's on the list) wrote an artcle about this for gamasutra:

http://www.gamasutra.com/features/19990813/languages_01.htm

Chris




  reply	other threads:[~2001-01-07 20:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-02 16:07 Markus Mottl
2001-01-02 18:16 ` Mattias Waldau
2001-01-02 19:30   ` Markus Mottl
2001-01-03 12:15     ` Alain Frisch
2001-01-04  8:37       ` Fabrice Le Fessant
2001-01-04  9:04         ` Alain Frisch
2001-01-03 13:23     ` Mattias Waldau
2001-01-03 14:25       ` Markus Mottl
2001-01-03 14:40       ` STARYNKEVITCH Basile
2001-01-03 15:51     ` John Max Skaller
2001-01-03 17:50       ` Markus Mottl
2001-01-05  0:30         ` Michael Hicks
2001-01-08  9:59           ` Xavier Leroy
2001-01-09  6:40         ` John Max Skaller
2001-01-03 17:49     ` Joseph R. Kiniry
2001-01-03 18:19       ` Markus Mottl
2001-01-03 18:38         ` Joseph R. Kiniry
2001-01-03 18:58           ` Markus Mottl
2001-01-03 19:06             ` Joseph R. Kiniry
2001-01-04 22:32               ` Jonathan Coupe
2001-01-07  0:16                 ` Chris Hecker [this message]
2001-01-05 12:52               ` Sven LUTHER
2001-01-05 20:08                 ` Joseph R. Kiniry
2001-01-09  7:14             ` John Max Skaller
2001-01-09  6:50         ` John Max Skaller
2001-01-05 12:39   ` Sven LUTHER
2001-01-05  5:48 ` Vitaly Lugovsky
2001-01-03 15:24 Jerry Jackson
2001-01-04 14:12 ` Alan Schmitt
2001-01-09 17:09 Dave Berry
2001-01-11  6:38 ` John Max Skaller
2001-01-09 17:18 Dave Berry
2001-01-11  7:00 ` John Max Skaller
2001-01-11 10:01   ` Alain Frisch
2001-01-12  7:55     ` John Max Skaller
2001-01-11 12:45 Dave Berry
2001-01-12  8:23 ` John Max Skaller

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=4.3.2.7.2.20010106160502.00bb4390@shell16.ba.best.com \
    --to=checker@d6.com \
    --cc=caml-list@inria.fr \
    --cc=jonathan@meanwhile.freeserve.co.uk \
    --cc=kiniry@acm.org \
    /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).