From: Warp <warplayer@free.fr>
To: Sven Luther <luther@dpt-info.u-strasbg.fr>
Cc: jeanmarc.eber@lexifi.com,
Sven Luther <luther@dpt-info.u-strasbg.fr>,
achrist@easystreet.com, caml-list@inria.fr
Subject: Re: [Caml-list] OCaml on Windows please advise
Date: Sat, 09 Nov 2002 18:20:29 +0100 (CET) [thread overview]
Message-ID: <1036862429.3dcd43ddeffb9@imp.free.fr> (raw)
In-Reply-To: <20021108204733.GA4958@iliana>
[...]
> > > But windows only :(((
> > >
> > > Friendly,
> > >
> > > Sven Luther
> >
> > What's the problem about that ? Why :(((( ?
> > Isn't it fine that ocaml is used *natively* on the win32 platform also
> ?
>
> Yes, but that would mean that the apps developped for it will only be
> usable for on windows only, which let many people out in the cold. In
> particular, i would love to play a ocaml based games, not that i have
> time for it but still, but since i don't have windows, ...
>
> Also, i remember when i was some time back at the AFIG conference,
> there
> where the people making the outcast games explaining how they did
> their
> software rendering and all, and i asked them about a linux port, since
> they software was not using any hardware acceleration, in these
> pre-DRI
> times it would have been a good candidate for a linux port. They
> esquived my question, and look where they are now ? Maybe the
> publicity
> coup they would have made with releasing a linux games would have
> saved
> them.
That's an OT subject... almost troll :)
Back to the thread, I would say that to port of such a game would only need the
port of the C 3D functions DLL based on the OCaml interface which could be
disclosed without the need to release the entire game source code ( often a
problem for us industrials - no flames please ). And actually only people
building the game care about the R&D tools, which can also be built by porting
Osiris to *Nix systems ( eg by using GTK ).
OCaml so is really useful because you only need to take care of the low-level
library port ( which can be open sourced if you release only the interfaces )
which is a pretty good compromise for both industrials and end users.
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
prev parent reply other threads:[~2002-11-09 17:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 21:23 isaac gouy
2002-11-04 23:46 ` SooHyoung Oh
2002-11-05 18:21 ` Nicolas Cannasse
2002-11-05 18:12 ` achrist
2002-11-06 5:53 ` Eric Mangold
2002-11-06 19:54 ` Nicolas Cannasse
2002-11-06 19:58 ` achrist
2002-11-06 20:31 ` jeanmarc.eber
2002-11-07 8:30 ` Xavier Leroy
2002-11-08 0:20 ` achrist
2002-11-08 18:41 ` Nicolas Cannasse
2002-11-08 18:14 ` Sven Luther
2002-11-08 20:20 ` jeanmarc.eber
2002-11-08 20:47 ` Sven Luther
2002-11-08 22:43 ` malc
2002-11-08 23:02 ` Sven Luther
2002-11-08 23:47 ` malc
2002-11-09 1:00 ` Eric Mangold
2002-11-09 1:21 ` malc
2002-11-09 7:13 ` Sven Luther
2002-11-09 9:17 ` Olivier Andrieu
2002-11-09 10:08 ` Sven Luther
2002-11-12 13:28 ` Olivier Andrieu
2002-11-09 17:20 ` Warp [this message]
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=1036862429.3dcd43ddeffb9@imp.free.fr \
--to=warplayer@free.fr \
--cc=achrist@easystreet.com \
--cc=caml-list@inria.fr \
--cc=jeanmarc.eber@lexifi.com \
--cc=luther@dpt-info.u-strasbg.fr \
/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