caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: malc <malc@pulsesoft.com>
To: Sven Luther <luther@dpt-info.u-strasbg.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml on Windows please advise
Date: Sat, 9 Nov 2002 02:47:40 +0300 (MSK)	[thread overview]
Message-ID: <Pine.LNX.4.44.0211090244280.3339-100000@home.oyster.ru> (raw)
In-Reply-To: <20021108230242.GA4100@iliana>

On Sat, 9 Nov 2002, Sven Luther wrote:

> On Sat, Nov 09, 2002 at 01:43:48AM +0300, malc wrote:

> > Hands off Outcast please. Besides i doubt that Appeal's failure has 
> > anything to do with Outcast being windows only. And btw Outcast was 
> > instrumental in one person's switch to OCaml.
> 
> Ok, no problem, it was just one thing that came to mind when thinking
> about this, since i recently read of Appeal's demise and remembered this
> discution. That said, i believe that their rendering engine could have
> easily been ported, more easily that other hardware accelerated engines
> of that time at least.
> 
> That said, jean marc asked if it wasn't fine to have ocaml used
> *natively* on the win32 plateform, and i believe it would be nice, but
> would create the risk of win32 only ocaml programs, which is IMHO not a
> nice thing to contemplate.
> 
> > P.S. http://algol.prosalg.no/~malc/motazaar/
> 
> Mmm, i see it uses GTK+, it would run on linux too then ?

It was developed under Linux, Windows version was, quite painful,
afterthought. Btw. i advice everyone to stay as far away of GTK+ as 
possible(esp. under Windows)

-- 
mailto:malc@pulsesoft.com

-------------------
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-11-08 23:46 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 [this message]
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

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=Pine.LNX.4.44.0211090244280.3339-100000@home.oyster.ru \
    --to=malc@pulsesoft.com \
    --cc=caml-list@inria.fr \
    --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;
as well as URLs for NNTP newsgroup(s).