Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Chris Hecker <checker@d6.com>
To: "Mattias Waldau" <mattias.waldau@abc.se>,
	"'Alain Frisch'" <frisch@clipper.ens.fr>
Cc: "'Caml list'" <caml-list@inria.fr>
Subject: RE: [Caml-list] The DLL-hell of O'Caml
Date: Sat, 02 Mar 2002 14:41:12 -0800	[thread overview]
Message-ID: <4.3.2.7.2.20020302143944.032a73f0@mail.d6.com> (raw)
In-Reply-To: <000001c1c222$6ae16ec0$0700a8c0@gateway>


>apt-get, interesting idea. (does it work for windows?)

I doubt it, but it probably wouldn't be that hard to port (he says, 
cluelessly).

>compilation and windows is a problem.

Right, good point, I forgot about that.  Although, that does imply we're 
targeting both developers and users, which will make things harder.

 > I got the impression that the byte-code is compatible between
>different platforms (Is this true?)

I believe this is true.

Chris

-------------------
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-03-02 22:45 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01 18:52 [Caml-list] troubleshooting problem related to garbage collection james woodyatt
2002-03-02  0:11 ` james woodyatt
2002-03-02  7:57   ` [Caml-list] The DLL-hell of O'Caml Mattias Waldau
2002-03-02 11:56     ` Markus Mottl
2002-03-02 21:40       ` Alexander V. Voinov
2002-03-02 14:46     ` Alain Frisch
2002-03-02 19:00       ` Chris Hecker
2002-03-02 19:42         ` Mattias Waldau
2002-03-02 22:41           ` Chris Hecker [this message]
2002-03-03 15:56             ` Vitaly Lugovsky
2002-03-04  9:57           ` Sven
2002-03-04 12:10             ` possible solution to " Dave Mason
2002-03-05  7:58               ` Mattias Waldau
2002-03-05 12:47                 ` Dave Mason
2002-03-04 12:20     ` Jacques Garrigue
2002-03-11  4:28 Mark D. Anderson
2002-03-11  7:12 ` Mattias Waldau
2002-03-11 12:15 ` Gerd Stolpmann
2002-03-12  0:19   ` Jeff Henrikson
2002-03-12 22:00     ` Gerd Stolpmann
2002-03-20 11:20       ` Fergus Henderson
2002-03-20 11:43         ` Jacques Garrigue
2002-03-20 17:16           ` Fergus Henderson
2002-03-20 12:53         ` Gerd Stolpmann
2002-03-20 13:05           ` Johan Georg Granström
2002-03-20 13:40             ` Gerd Stolpmann
2002-03-20 19:46               ` Alain Frisch
2002-03-20 20:39               ` Xavier Leroy
2002-03-20 21:16                 ` Markus Mottl
2002-03-21  9:07                 ` Warp
2002-03-21 10:18                 ` Christopher Quinn
2002-03-21 18:13                   ` Xavier Leroy
2002-03-21 14:13                 ` Jeff Henrikson
2002-03-21 18:10                   ` Xavier Leroy
2002-03-21 18:39                     ` Sven
2002-03-21 19:22                     ` james woodyatt
2002-03-21 19:43                     ` Jeff Henrikson
2002-03-22  2:02                     ` Brian Rogoff
2002-03-22 10:11                     ` Warp
2002-03-21 18:50                 ` Sven
2002-03-22 10:14 Dave Berry
2002-03-22 10:24 Dave Berry

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.20020302143944.032a73f0@mail.d6.com \
    --to=checker@d6.com \
    --cc=caml-list@inria.fr \
    --cc=frisch@clipper.ens.fr \
    --cc=mattias.waldau@abc.se \
    /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