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: Wed, 1 Sep 2004 10:17:55 -0700	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDAEINHHAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <OOEALCJCKEBJBIJHCNJDIEILHHAB.vanevery@indiegamedesign.com>

Brandon J. Van Every wrote:
> The Caml Trade wrote:
>
> > I think you have your priorities crossed.  Lots of good
> > code migrates
> > out of the Unix culture into the Windows development world, but it
> > historically *never* happens when Unix-centric people push—
> > only when Windows-centric people pull.
>
> Mono
> concept of installation packages
> most commercial digital media editing software
> most games
>
> My stereotype of a UNIX guy is someone who likes to play with text
> editors all day long.

I suppose I missed that you were talking about *code* migration, as
opposed to who's the progenitor of what technology on what platform.
The phenomenon you describe of "which whay the code flows" is largely
true.  After all, Windows people can and do buy commercial apps that get
their jobs done.  A lot of invention of capability happens on Windows,
in proprietary commercial software.  Then UNIX guys clone it, if they
can tear themselves away from their text editors.  Leaving open source
vs. proprietary aside, there are arenas in which UNIX developers are
mostly responsible for the innovations, and arenas where Windows
developers are.  Which OS one gravitates towards is largely a matter of
problem domain.  I think it would be silly to look to UNIX for game or
3D graphics code.


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


  reply	other threads:[~2004-09-01 17:08 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
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 [this message]
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=OOEALCJCKEBJBIJHCNJDAEINHHAB.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).