caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "caml" <caml-list@inria.fr>
Subject: RE: [Caml-list] Cross-compiling OCaml
Date: Tue, 31 Aug 2004 12:30:54 -0700	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDKEHGHHAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <200408310841.18106.jgoerzen@complete.org>

John Goerzen wrote:
> Brandon J. Van Every wrote:
> >
> > I'm just objecting to the statement that Linux cross-compilation
> > support [for Windows] "would indeed be a great great additional
> > functionality."
>
> Well, let's look at that, because I believe you are missing the point.
>
> Who ever said that cross-compilation support would only
> involve running
> a compiler on x86 Linux to target x86 Windows?

Ken Rose originally said:
>
> Is there any support for cross-compilation of OCaml?  In
> particular, I'd
> like to build Windows binaries on my x86 Linux box, preferrably with
> ocamlopt.

If you want to make other points about other kinds of cross-compilation,
that's great, but it doesn't mean I'm "missing the point."  We've been
talking about the utility of cross-compilation from Linux to Windows.

> > I think the reason you should care is because Windows is a big
> > platform with a lot of users.  If you want to see the use of OCaml
>
> Why should that make us care?  Why must you persist in measuring the
> success or failure of everything on pure user count?  I would
> say that
> is a pretty damn poor way to measure success, if not a completely
> stupid one.

So you want the future of OCaml to look like the present of Lisp then?
Those who don't study history are doomed to repeat it.

> In that case, please explain the popularity of Perl, Python,
> sed, awk,
> Tcl, and Bourne shell.  All of which have had for a long time, or
> continue to have, roughly the same level of support for Windows as
> OCaml does.  Or less.

I don't agree with your characterization of OCaml's Windows support as
being "equal to" these other languages.  Python, in particular, can be
pretty seamlessly cross-platform.  At any rate, feel free to hop over to
http://wiki.cocan.org/ocaml_alliance, skip down to the "Shallower
learning-curve for Windows" section, and start enlightening us.

> I think that offering a simple tarball with the source is just fine.

I'd try to explain the importance of source control, multiple
contributors, active mailing lists, site indexing, explanatory webpages,
a user base, etc., but I did that already, so this is sounding like a
lost cause.


Cheers,                         www.indiegamedesign.com
Brand*n Van Every               S*attle, WA

Praise Be to the caml-list Bayesian filter! It blesseth
my postings, it is evil crap!  evil crap!  Bigarray!
Unboxed overhead group!  Wondering!  chant chant chant...

Is my technical content showing?

// return an array of 100 packed tuples
temps
  int $[tvar0][2*100]; // what the c function needs
  value $[tvar1]; // one int
  value $[tvar2]; // one tuple
  int $[tvar3] // loop control var
oncePre
eachPre
  $[cvar0]=&($[tvar0][0]);
eachPost
  $[lvar0] = alloc(2*100, 0 /*NB: zero-tagged block*/ );
  for(int $[tvar3]=0;$[tvar3]<100;$[tvar3]++) {
    $[tvar2] = alloc_tuple(2);
    $[tvar1] = Val_int($[cvar0][0+2*$[tvar3]]);
    Store_field($[tvar2],0,$[tvar1]);
    $[tvar1] = Val_int($[cvar0][1]);
    Store_field($[tvar2],1,$[tvar1+2*$[tvar3]]);
    Array_store($[lvar0],$[tvar3],$[tvar0]);
  }
oncePost

-------------------
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


  parent reply	other threads:[~2004-08-31 19:20 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30 21:02 Ken Rose
2004-08-30 21:30 ` Erik de Castro Lopo
2004-08-31  6:09 ` Sven Luther
2004-08-31  6:50   ` Brandon J. Van Every
2004-08-31  7:14     ` james woodyatt
2004-08-31  9:05       ` Brandon J. Van Every
2004-08-31 13:41         ` John Goerzen
2004-08-31 15:56           ` Ken Rose
2004-08-31 19:30           ` Brandon J. Van Every [this message]
2004-09-01  0:05           ` Christopher A. Watford
2004-09-01  7:53             ` Sven Luther
2004-09-01  7:32         ` james woodyatt
2004-09-01 16:38           ` Brandon J. Van Every
2004-09-01 17:17             ` Brandon J. Van Every
2004-09-01 22:56               ` Sven Luther
2004-09-01 17:32             ` John Goerzen
2004-09-02 21:24             ` I R T
2004-08-31  7:16     ` Sven Luther
2004-08-31  9:05       ` Brandon J. Van Every
2004-08-31  9:18         ` Sven Luther
2004-08-31  9:41           ` Brandon J. Van Every
2004-08-31 15:17           ` skaller
2004-08-31 16:49             ` Sven Luther
2004-08-31 13:48         ` John Goerzen
2004-09-01 13:22         ` I R T
2004-08-31 13:56           ` Erik de Castro Lopo
2004-08-31 13:29     ` John Goerzen
2004-08-31 14:06       ` Erik de Castro Lopo
2004-08-31 15:48         ` skaller
2004-08-31 15:54         ` John Goerzen
2004-08-31 22:49           ` Jon Harrop
2004-08-31 23:36             ` Benjamin Geer
2004-09-01  8:08             ` Erik de Castro Lopo
2004-09-02 11:30               ` Richard Jones
2004-09-09  1:46               ` Jon Harrop
2004-09-01  4:05           ` skaller
2004-09-01  8:45             ` Erik de Castro Lopo
2004-09-01  7:40           ` Erik de Castro Lopo
2004-08-31 19:11       ` Brandon J. Van Every
2004-09-01 21:18         ` I R T
2004-08-31 22:36           ` [Caml-list] game development Brandon J. Van Every
2004-09-01 23:28             ` I R T
2004-09-01  0:37               ` Brandon J. Van Every
2004-08-31 18:34     ` [Caml-list] Cross-compiling OCaml brogoff
2004-08-31 21:07       ` [Caml-list] OCaml's critical mass Brandon J. Van Every
     [not found] <Pine.LNX.4.44.0408312302560.3196-100000@localhost>
2004-08-31 20:04 ` [Caml-list] Cross-compiling OCaml Brandon J. Van Every
     [not found] <AA48BAF0-FC3A-11D8-8C25-000A958FF2FE@wetware.com>
2004-09-01 18:37 ` Brandon J. Van Every
2004-09-01 19:45   ` John Goerzen
2004-09-01 21:16     ` Brandon J. Van Every

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=OOEALCJCKEBJBIJHCNJDKEHGHHAB.vanevery@indiegamedesign.com \
    --to=vanevery@indiegamedesign.com \
    --cc=caml-list@inria.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).